Quoting Jack Howarth <howa...@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
