On Thu, Jun 07, 2007 at 12:10:26PM +0200, Jan-Benedict Glaw wrote:
> On Wed, 2007-06-06 22:44:17 +0100, James Youngman <[EMAIL PROTECTED]> wrote:
> > If I read a stream of data (from a file, a network socket, etc.) which
> > is supposed to contain valid floating-point data, it is reasonable for
> >
at pass arbitrary bit patterns read from an insecure
source to *printf and other functions are definitely
broken as floating point numbers, they can hit signalling NaNs etc.
2007-06-06 Jakub Jelinek <[EMAIL PROTECTED]>
BZ #4586
* sysdeps/i386/ldbl2mpn.c (__mpn_extract
leading_period variable. Either the code will always
return without ever looking at that var again (that was the only case
before this patch), or it will reinitialize it from what the recursive
call passed up.
2007-03-27 Jakub Jelinek <[EMAIL PROTECTED]>
* posix/fnmatch.c (S
On Sun, Feb 11, 2007 at 09:51:33PM -0800, Paul Eggert wrote:
> > Given that there is still discussion and work on GCC for this topic
> > anyway[1], I don't think Autoconf should be doing anything just yet.
Yeah, it is just too early.
> Both of the solutions that Bruno suggested seem too drastic t
On Wed, Nov 30, 2005 at 09:53:53PM +0100, Jim Meyering wrote:
> Roland McGrath <[EMAIL PROTECTED]> wrote:
> > I think that the Solaris *at functions were really primarily intended for
> > use with O_XATTR to get at "file attribute" magic pseudo-directories rather
> > than to optimize use of normal
