glibc segfault on "special" long double values is _ok_!?

[Nix]

On 8 Jun 2007, Jeremy Linton verbalised:

> James Youngman wrote:
>> On 6/8/07, Nix <nix@esperi.org.uk> wrote:
>
>>> I'd say this behaviour violates the principle of least astonishment, at
>>> least. Mind you, avoiding it does seem like it could be expensive: [...]
>> Maybe.  For the issue-diagnostic-message use case, performance is not
>> such an issue.  But I'm sure there are valid use cases where ultimate
>> performance is really vital.  Use-cases vary a lot.
>
> 	I sort of doubt that anyone who really cares about performance is calling printf...

printf(), no. *s*printf(), maybe (although given how slow some printf()s
can be they're in for a shock on some platforms if they try).

-- 
`... in the sense that dragons logically follow evolution so they would
 be able to wield metal.' --- Kenneth Eng's colourless green ideas sleep
 furiously