public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "laurent at guerby dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/45067] [4.6 regression] ARM bootstrap failure: internal compiler error: in expand_widen_pattern_expr, at optabs.c:522
Date: Thu, 02 Sep 2010 14:29:00 -0000	[thread overview]
Message-ID: <20100902142903.3778.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45067-7665@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from laurent at guerby dot net  2010-09-02 14:29 -------
Last succesful arm bootstrap for my tester is r163026.

At r163046 it fails with :
<<
/home/guerby/build/./prev-gcc/xgcc -B/home/guerby/build/./prev-gcc/
-B/n/57/guerby/install-trunk-163046/armv5tel-unknown-linux-gnueabi/bin/
-B/n/57/guerby/install-trunk-163046/armv5tel-unknown-linux-gnueabi/bin/
-B/n/57/guerby/install-t\
runk-163046/armv5tel-unknown-linux-gnueabi/lib/ -isystem
/n/57/guerby/install-trunk-163046/armv5tel-unknown-linux-gnueabi/include
-isystem
/n/57/guerby/install-trunk-163046/armv5tel-unknown-linux-gnueabi/sys-include   
-c   -g -O2 -gtog\
gle -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 -Werror -Wold-style-definition
-Wc++-compat -f\
no-common  -DHAVE_CONFIG_H -I. -I. -I../../trunk/gcc -I../../trunk/gcc/.
-I../../trunk/gcc/../include -I../../trunk/gcc/../libcpp/include 
-I../../trunk/gcc/../libdecnumber -I../../trunk/gcc/../libdecnumber/dpd
-I../libdecnumber     \
                ../../trunk/gcc/config/arm/arm.c -o arm.o
../../trunk/gcc/config/arm/arm.c: In function 'arm_get_pcs_model':
../../trunk/gcc/config/arm/arm.c:3720:7: error: passing argument 1 of
'stdarg_p' discards 'const' qualifier from pointer target type [-Werror]
../../trunk/gcc/tree.h:4829:13: note: expected 'tree' but argument is of type
'const_tree'
cc1: all warnings being treated as errors

make[3]: *** [arm.o] Error 1
make[3]: Leaving directory `/home/guerby/build/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory `/home/guerby/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/home/guerby/build'
make: *** [bootstrap] Error 2
>>

Then starting with r163281 the failure changes:
<<
/home/guerby/build/./prev-gcc/xgcc -B/home/guerby/build/./prev-gcc/
-B/n/57/guerby/install-trunk-163281/armv5tel-unknown-linux-gnueabi/bin/
-B/n/57/guerby/install-trunk-163281/armv5tel-unknown-linux-gnueabi/bin/
-B/n/57/guerby/install-t\
runk-163281/armv5tel-unknown-linux-gnueabi/lib/ -isystem
/n/57/guerby/install-trunk-163281/armv5tel-unknown-linux-gnueabi/include
-isystem
/n/57/guerby/install-trunk-163281/armv5tel-unknown-linux-gnueabi/sys-include   
-c   -g -O2 -gtog\
gle -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 -Werror -Wold-style-definition
-Wc++-compat -f\
no-common  -DHAVE_CONFIG_H -I. -I. -I../../trunk/gcc -I../../trunk/gcc/.
-I../../trunk/gcc/../include -I../../trunk/gcc/../libcpp/include 
-I../../trunk/gcc/../libdecnumber -I../../trunk/gcc/../libdecnumber/dpd
-I../libdecnumber     ins\
n-attrtab.c -o insn-attrtab.o
../../trunk/gcc/config/arm/arm.md: In function 'get_attr_enabled':
../../trunk/gcc/config/arm/arm.md:178:4: error: enum conversion in return is
invalid in C++ [-Werror=c++-compat]
../../trunk/gcc/config/arm/arm.md:191:4: error: enum conversion in return is
invalid in C++ [-Werror=c++-compat]
../../trunk/gcc/config/arm/arm.md:199:7: error: enum conversion in return is
invalid in C++ [-Werror=c++-compat]
cc1: all warnings being treated as errors

make[3]: *** [insn-attrtab.o] Error 1
make[3]: Leaving directory `/home/guerby/build/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory `/home/guerby/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/home/guerby/build'
make: *** [bootstrap] Error 2
>>

Last revision I tested (with the above failure) is r163437, I've now relaunched
my tester.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45067


  parent reply	other threads:[~2010-09-02 14:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 13:02 [Bug bootstrap/45067] New: " mikpe at it dot uu dot se
2010-07-25 13:02 ` [Bug bootstrap/45067] " mikpe at it dot uu dot se
2010-07-25 16:14 ` mikpe at it dot uu dot se
2010-07-25 19:24 ` mikpe at it dot uu dot se
2010-07-26  8:55 ` ramana at gcc dot gnu dot org
2010-07-26 10:22 ` rguenth at gcc dot gnu dot org
2010-07-27 12:32 ` ramana at gcc dot gnu dot org
2010-07-28  8:11 ` mkuvyrkov at gcc dot gnu dot org
2010-07-30  9:37 ` ramana at gcc dot gnu dot org
2010-08-01  9:53 ` laurent at guerby dot net
2010-08-07 11:59 ` mikpe at it dot uu dot se
2010-09-02 11:09 ` rguenth at gcc dot gnu dot org
2010-09-02 14:29 ` laurent at guerby dot net [this message]
2010-09-03  6:26 ` laurent at guerby dot net
2010-09-04 16:19 ` mikpe at it dot uu dot se

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100902142903.3778.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).