public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44790] New: Bootstrap fails after MEM-REF merge Date: Fri, 02 Jul 2010 18:53:00 -0000 [thread overview] Message-ID: <bug-44790-3107@http.gcc.gnu.org/bugzilla/> (raw) GCC fails to bootstrap on ia64-hp-hpux11.23 after r161655. Building without bootstrap and running the testsuite shows that tests are failing in 32 bit mode but not 64 bit mode so the problem is probably ia64's unique method of extending pointers in 32 bit mode Most of the failing tests involve va_args. Here is a cutdown test that fails: f (int n, ...) { long x; int i; __builtin_va_list ap; __builtin_va_start(ap,n); x = __builtin_va_arg(ap,long); if (x != 123) abort(); __builtin_va_end(ap); } main () { f (3, (long) 123); exit(0); } -- Summary: Bootstrap fails after MEM-REF merge Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sje at cup dot hp dot com GCC build triplet: ia64-hp-hpux11.23 GCC host triplet: ia64-hp-hpux11.23 GCC target triplet: ia64-hp-hpux11.23 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44790
next reply other threads:[~2010-07-02 18:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-02 18:53 sje at cup dot hp dot com [this message] 2010-07-02 19:49 ` [Bug middle-end/44790] " sje at cup dot hp dot com 2010-07-03 11:17 ` rguenth at gcc dot gnu dot org 2010-07-06 14:26 ` [Bug middle-end/44790] [4.6 Regression] " rguenth at gcc dot gnu dot org 2010-07-06 16:44 ` sje at cup dot hp dot com 2010-07-06 22:56 ` sje at cup dot hp dot com 2010-07-07 8:35 ` rguenther at suse dot de 2010-07-07 12:44 ` rguenth at gcc dot gnu dot org 2010-07-07 13:04 ` rguenth at gcc dot gnu dot org 2010-07-28 7:45 ` ebotcazou 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-44790-3107@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).