public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/32522] New: Bootstrap failure on Alpha due to pointer-plus changes Date: Wed, 27 Jun 2007 15:46:00 -0000 [thread overview] Message-ID: <bug-32522-2744@http.gcc.gnu.org/bugzilla/> (raw) src/gcc-2007.06.27/build/./gcc/xgcc -B/src/gcc-2007.06.27/build/./gcc/ -B/usr/local/alphaev68-unknown-linux-gnu/bin/ -B/usr/local/alphaev68-unknown-linux-gnu/lib/ -isystem /usr/local/alphaev68-unknown-linux-gnu/include -isystem /usr/local/alphaev68-unknown-linux-gnu/sys-include -g -fkeep-inline-functions -O2 -O2 -g -O2 -mieee -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -mieee -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../.././gcc -I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc -I../../../libgcc/../include -o _gcov_execl.o -MT _gcov_execl.o -MD -MP -MF _gcov_execl.dep -DL_gcov_execl -c ../../../libgcc/../gcc/libgcov.c ../../../libgcc/../gcc/libgcov.c: In function '__gcov_execl': ../../../libgcc/../gcc/libgcov.c:838: internal compiler error: in build2_stat, at tree.c:3074 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. make[3]: *** [_gcov_execl.o] Error 1 make[3]: Leaving directory `/src/gcc-2007.06.27/build/alphaev68-unknown-linux-gnu/libgcc' This happens as soon as varargs are used: $ cat test.c void f(int x, ...) { __builtin_va_list ap; __builtin_va_start(ap, x); } $ /src/gcc-2007.06.27/build/gcc/xgcc -B/src/gcc-2007.06.27/build/gcc/ -c test.c test.c: In function 'f': test.c:3: internal compiler error: in build2_stat, at tree.c:3074 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. Apparently, the Alpha backend needs to adapt to the pointer-plus changes. -- Summary: Bootstrap failure on Alpha due to pointer-plus changes Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: falk at debian dot org GCC build triplet: alphaev68-unknown-linux-gnu GCC host triplet: alphaev68-unknown-linux-gnu GCC target triplet: alphaev68-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32522
next reply other threads:[~2007-06-27 15:46 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-27 15:46 falk at debian dot org [this message] 2007-06-27 22:57 ` [Bug target/32522] [4.3 Regression] " pinskia at gcc dot gnu dot org 2007-06-29 18:56 ` mmitchel at gcc dot gnu dot org 2007-07-05 13:01 ` falk at debian dot org 2007-07-05 18:48 ` pinskia at gcc dot gnu dot org 2007-07-12 21:01 ` pinskia at gcc dot gnu dot org 2007-07-16 16:41 ` ro at gcc dot gnu dot org 2007-07-16 17:30 ` belyshev at depni dot sinp dot msu dot ru 2007-07-17 11:28 ` ro at techfak dot uni-bielefeld dot de 2007-07-26 19:49 ` belyshev at depni dot sinp dot msu dot ru 2007-07-26 22:50 ` falk at debian dot org 2007-07-27 6:18 ` belyshev at depni dot sinp dot msu dot ru 2007-07-27 6:22 ` patchapp at dberlin dot org 2007-07-29 2:00 ` pinskia at gcc dot gnu dot org 2007-08-20 6:53 ` pinskia at gcc dot gnu dot org 2007-08-20 6:53 ` pinskia at gcc dot gnu dot org
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=bug-32522-2744@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).