On Tue, Apr 10, 2012 at 9:08 PM, NightStrike <nightstr...@gmail.com> wrote:
> On Tue, Apr 10, 2012 at 10:38 AM, Richard Guenther
> <richard.guent...@gmail.com> wrote:
>> On Tue, Apr 10, 2012 at 3:06 PM, JonY <jo...@users.sourceforge.net> wrote:
>>> On 4/10/2012 20:37, Richard Guenther wrote:
>>>> On Tue, Apr 10, 2012 at 2:15 PM, JonY wrote:
>>>>> Patch OK?
>>>> What kind of warning?
>>> Oops, I forgot to mention gcc was complaining about missing braces.
>> Not for me. And I fail to see why it should.
> This is the warning:
> ../../../../build/gcc/src/gcc/tree-parloops.c:724: warning: suggest
> explicit braces to avoid ambiguous `else'
> ./xgcc -B. -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual
> -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic
> -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
> -Wold-style-definition -Wc++-compat -fno-common -DHAVE_CONFIG_H -I. -I.
> -I/space/rguenther/src/svn/trunk/gcc -I/space/rguenther/src/svn/trunk/gcc/.
> -I/space/rguenther/src/svn/trunk/gcc/../libdecnumber/bid -I../libdecnumber
> /space/rguenther/src/svn/trunk/gcc/tree-parloops.c -o tree-parloops.o
no warning from trunk. Which GCC version emits this warning? Note that
we do not try to keep stage1 warning-free but only later stages (which is
why we use -Werror there).