Date: Sun, 21 Sep 2014 19:20:49 -0700 From: Rui Paulo <rpaulo@me.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-toolchain@freebsd.org Subject: Re: Is this a compiler bug? Message-ID: <2EB3354D-0F65-4A79-A378-7F397911284A@me.com> In-Reply-To: <20140922014853.GA4469@troutmask.apl.washington.edu> References: <20140922011946.GA4317@troutmask.apl.washington.edu> <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> <20140922014853.GA4469@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 21, 2014, at 18:48, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
> On Sun, Sep 21, 2014 at 06:38:48PM -0700, Rui Paulo wrote:
>> On Sep 21, 2014, at 18:19, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
>>>
>>> #include <stdio.h>
>>> #include <stdint.h>
>>>
>>> int
>>> main(void)
>>> {
>>> uint16_t i;
>>> i = 0x3ff0+63; printf("%x\n", i);
>>> i = 0x3ff1+63; printf("%x\n", i);
>>> i = 0x3ff2+63; printf("%x\n", i);
>>> i = 0x3ff3+63; printf("%x\n", i);
>>> i = 0x3ff4+63; printf("%x\n", i);
>>> i = 0x3ff4+63; printf("%x\n", i);
>>> i = 0x3ff6+63; printf("%x\n", i);
>>> i = 0x3ff7+63; printf("%x\n", i);
>>> i = 0x3ff8+63; printf("%x\n", i);
>>> i = 0x3ff9+63; printf("%x\n", i);
>>> i = 0x3ffa+63; printf("%x\n", i);
>>> i = 0x3ffb+63; printf("%x\n", i);
>>> i = 0x3ffc+63; printf("%x\n", i);
>>> i = 0x3ffd+63; printf("%x\n", i);
>>> i = 0x3ffe+63; printf("%x\n", i);
>>> i = 0x3fff+63; printf("%x\n", i);
>>> return 0;
>>> }
>>
>> Looks like it. Please file a bug report with LLVM.
>>
>
> Unfortunately, llvm requires an account to report bugs.
I think I know what's happening: "e" is being parsed as scientific notation.
--
Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2EB3354D-0F65-4A79-A378-7F397911284A>