Re: Suspicious warning in W64 build

[Richard Copley <rcopley@gmail.com>]

On 7 September 2017 at 20:00, Angelo Graziosi <angelo.g0@libero.it> wrote:
> Richard.
>
>> Il 7 settembre 2017 alle 19.58 Richard Copley <rcopley@gmail.com> ha scritto:
>>
>>
>> On 7 September 2017 at 18:52, Richard Copley <rcopley@gmail.com> wrote:
>> > On 7 September 2017 at 16:42, Angelo Graziosi <angelo.g0@libero.it> wrote:
>> >>> Il 7 settembre 2017 alle 17.16 Eli Zaretskii <eliz@gnu.org> ha scritto:
>> >>> > Date: Tue, 5 Sep 2017 15:38:15 +0200 (CEST)
>> >>> > From: Angelo Graziosi <angelo.g0@libero.it>
>> >>> >
>> >>> > In the log build of current master on MSYS2/MINGW64, I see:
>> >>> >
>> >>> > [...]
>> >>> > CC       w32term.o
>> >>> > C:/msys64/tmp/src/src/w32font.c: In function 'w32font_text_extents':
>> >>> > C:/msys64/tmp/src/src/w32font.c:547:9: warning: argument 1 range [18446744065119617024, 18446744073709551612] exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=]
>> >>> >    wcode = alloca (nglyphs * sizeof (WORD) * 2);
>> >>> >          ^
>> >>> > C:/msys64/tmp/src/src/w32font.c:547:9: note: in a call to built-in allocation function '__builtin_alloca'
>> >>>
>> >
>> >>> Where did it take these 2 numbers?
>> >
>> > I also see the warning (I use the same toolchain).
>> >
>> > 18446744065119617024 is 1<<64.
>> > The other number is (1<<64) - (1<<33) - (1<<2).
>> >
>> > That's just crazy. It must be a GCC bug.
>>
>> "https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79929".
>
> the link seems to have an "invalid" id...

No. My guess is that some software interpreted the link to include the
quotation mark and/or the full stop as part of the URL.

I put the URL in quotation marks to avoid the full stop being
interpreted as part of the URL. I suppose I'll start surrounding
URLs with newlines instead. Yuck!