public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* warnings as errors in gcc/gcc/config/i386/i386.c
@ 2010-07-10  5:45 Jack Howarth
  2010-07-10  7:12 ` Joern Rennecke
  0 siblings, 1 reply; 3+ messages in thread
From: Jack Howarth @ 2010-07-10  5:45 UTC (permalink / raw)
  To: gcc

  Is anyone seeing this issue on other targets? On x86_64-apple-darwin10,
with the patch...

Index: Makefile.in
===================================================================
--- Makefile.in (revision 162030)
+++ Makefile.in (working copy)
@@ -235,6 +235,7 @@
 POSTSTAGE1_CXX_EXPORT = \
        CXX="$(STAGE_CC_WRAPPER) $$r/$(HOST_SUBDIR)/prev-gcc/g++$(exeext) \
          -B$$r/$(HOST_SUBDIR)/prev-gcc/ -B$(build_tooldir)/bin/ -nostdinc++ \
+         -B$$r/prev-$(TARGET_SUBDIR)/libstdc++-v3/src/.libs \
          -I$$r/prev-$(TARGET_SUBDIR)/libstdc++-v3/include/$(TARGET_SUBDIR) \
          -I$$r/prev-$(TARGET_SUBDIR)/libstdc++-v3/include \
          -I$$s/libstdc++-v3/libsupc++ \

applied so that the --static-libstdc++ works in tree on darwin, I have
gotten the --enable-build-with-cxx bootstrap to progress to a later point
at which it fails with...

/Users/howarth/work/./prev-gcc/g++ -B/Users/howarth/work/./prev-gcc/ -B/Users/howarth/dist/x86_64-apple-darwin10.4.0/bin/ -nostdinc++ -B/Users/howarth/work/prev-x86_64-apple-darwin10.4.0/libstdc++-v3/src/.libs -I/Users/howarth/work/prev-x86_64-apple-darwin10.4.0/libstdc++-v3/include/x86_64-apple-darwin10.4.0 -I/Users/howarth/work/prev-x86_64-apple-darwin10.4.0/libstdc++-v3/include -I/Users/howarth/gcc/libstdc++-v3/libsupc++ -L/Users/howarth/work/prev-x86_64-apple-darwin10.4.0/libstdc++-v3/src/.libs -c  -g -O2 -gtoggle -DIN_GCC   -W -Wall -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror   -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I/sw/include -I/sw/include  -I../../gcc/gcc/../libdecnumber -I../../gcc/gcc/../libdecnumber/dpd -I../libdecnumber -I/sw/include  -I/sw/include -DCLOOG_PPL_BACKEND   -I/sw/include -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I/sw/include -I/sw/include  -I../../gcc/gcc/../libdecnumber -I../../gcc/gcc/../libdecnumber/dpd -I../libdecnumber -I/sw/include  -I/sw/include -DCLOOG_PPL_BACKEND   ../../gcc/gcc/config/host-darwin.c
In file included from ../../gcc/gcc/config/i386/i386.c:31581:0:
../../gcc/gcc/config/i386/i386.c: In function ‘tree_node* ix86_vectorize_builtin_vec_perm(tree, tree_node**)’:
../../gcc/gcc/config/i386/i386.c:30005:30: error: ‘fcode’ is used uninitialized in this function [-Werror=uninitialized]

The offending code in gcc/config/i386/i386.c appears to be...

static tree
ix86_vectorize_builtin_vec_perm (tree vec_type, tree *mask_type)
{
  tree itype = TREE_TYPE (vec_type);
  bool u = TYPE_UNSIGNED (itype);
  enum machine_mode vmode = TYPE_MODE (vec_type);
  enum ix86_builtins fcode = fcode; /* Silence bogus warning.  */
  bool ok = TARGET_SSE2;

Also, I don't seem able to suppress this build failure with...

../gcc/configure --prefix=/Users/howarth/dist --enable-languages=c,c++ --enable-build-with-cxx --with-gmp=/sw --with-libiconv-prefix=/sw --with-ppl=/sw --with-cloog=/sw --with-mpc=/sw --with-system-zlib --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib --enable-checking=release --disable-werror

Is that expected behavior in current gcc trunk?
              Jack

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: warnings as errors in gcc/gcc/config/i386/i386.c
  2010-07-10  5:45 warnings as errors in gcc/gcc/config/i386/i386.c Jack Howarth
@ 2010-07-10  7:12 ` Joern Rennecke
  2010-07-10 15:55   ` Jack Howarth
  0 siblings, 1 reply; 3+ messages in thread
From: Joern Rennecke @ 2010-07-10  7:12 UTC (permalink / raw)
  To: gcc

Quoting Jack Howarth <howarth@bromo.med.uc.edu>:

> Also, I don't seem able to suppress this build failure with...

I think fcode should be assigned some value in the default case instead.

> Is that expected behavior in current gcc trunk?

Strange, I just bootstrapped r162030 with a small unrelated change on gcc16
(x86_64-unknown-linux-gnu), and it didn't complain about this...

/home/amylaar/pr44874/bldxx/./prev-gcc/g++  
-B/home/amylaar/pr44874/bldxx/./prev-gcc/  
-B/home/amylaar/instxx/x86_64-unknown-linux-gnu/bin/ -nostdinc++  
-I/home/amylaar/pr44874/bldxx/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu -I/home/amylaar/pr44874/bldxx/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include -I/home/amylaar/pr44874/gcc/libstdc++-v3/libsupc++ -L/home/amylaar/pr44874/bldxx/prev-x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs -c  -g -O2 -gtoggle -DIN_GCC   -W -Wall -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common  -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I/opt/cfarm/mpfr-2.4.1/include -I/opt/cfarm/mpc-0.8/include  -I../../gcc/gcc/../libdecnumber -I../../gcc/gcc/../libdecnumber/bid -I../libdecnumber      
\
                 ../../gcc/gcc/config/i386/i386.c -o i386.o

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: warnings as errors in gcc/gcc/config/i386/i386.c
  2010-07-10  7:12 ` Joern Rennecke
@ 2010-07-10 15:55   ` Jack Howarth
  0 siblings, 0 replies; 3+ messages in thread
From: Jack Howarth @ 2010-07-10 15:55 UTC (permalink / raw)
  To: Joern Rennecke; +Cc: gcc

On Sat, Jul 10, 2010 at 03:11:51AM -0400, Joern Rennecke wrote:
> Quoting Jack Howarth <howarth@bromo.med.uc.edu>:
>
>> Also, I don't seem able to suppress this build failure with...
>
> I think fcode should be assigned some value in the default case instead.
>
>> Is that expected behavior in current gcc trunk?
>
> Strange, I just bootstrapped r162030 with a small unrelated change on gcc16
> (x86_64-unknown-linux-gnu), and it didn't complain about this...
>
> /home/amylaar/pr44874/bldxx/./prev-gcc/g++  
> -B/home/amylaar/pr44874/bldxx/./prev-gcc/  
> -B/home/amylaar/instxx/x86_64-unknown-linux-gnu/bin/ -nostdinc++  
> -I/home/amylaar/pr44874/bldxx/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu 
> -I/home/amylaar/pr44874/bldxx/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include 
> -I/home/amylaar/pr44874/gcc/libstdc++-v3/libsupc++ 
> -L/home/amylaar/pr44874/bldxx/prev-x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs 
> -c  -g -O2 -gtoggle -DIN_GCC   -W -Wall -Wwrite-strings -Wcast-qual 
> -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros 
> -Wno-overlength-strings -Werror -fno-common  -DHAVE_CONFIG_H -I. -I. 
> -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include 
> -I../../gcc/gcc/../libcpp/include -I/opt/cfarm/mpfr-2.4.1/include 
> -I/opt/cfarm/mpc-0.8/include  -I../../gcc/gcc/../libdecnumber 
> -I../../gcc/gcc/../libdecnumber/bid -I../libdecnumber     \
>                 ../../gcc/gcc/config/i386/i386.c -o i386.o

The change suggested by Iain Sandoe of...

Index: gcc/config/i386/i386.c
===================================================================
--- gcc/config/i386/i386.c      (revision 162037)
+++ gcc/config/i386/i386.c      (working copy)
@@ -30002,7 +30002,7 @@
   tree itype = TREE_TYPE (vec_type);
   bool u = TYPE_UNSIGNED (itype);
   enum machine_mode vmode = TYPE_MODE (vec_type);
-  enum ix86_builtins fcode = fcode; /* Silence bogus warning.  */
+  enum ix86_builtins fcode = IX86_BUILTIN_MAX;
   bool ok = TARGET_SSE2;

   switch (vmode)

eliminates the bootstrap failure on x86_64-apple-darwin10
when --enable-build-with-cxx is used..
                        Jack

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-07-10 15:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-07-10  5:45 warnings as errors in gcc/gcc/config/i386/i386.c Jack Howarth
2010-07-10  7:12 ` Joern Rennecke
2010-07-10 15:55   ` Jack Howarth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).