public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6597: ICE in set_mem_alias_set compiling Qt with -O2 on ia64 Date: Fri, 11 Oct 2002 11:46:00 -0000 [thread overview] Message-ID: <20021011184603.5240.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6597; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: janis187@us.ibm.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: optimization/6597: ICE in set_mem_alias_set compiling Qt with -O2 on ia64 Date: Fri, 11 Oct 2002 11:40:16 -0700 This ICE still occurs with GCC 3.3 20021008 (experimental) on ia64 when Qt is compiled with -O2. It's a regression from GCC 3.1. It doesn't occur when the mainline is built with checking disabled, so it won't show up in the release version unless GCC is built with checking enabled. Qt passes all of its tests when built with -O2 using mainline G++ built with checking disabled. The bug was introduced sometime between 20020228 and 20020315. GCC didn't build (even for a simple build of C and C++) on ia64-linux between those dates, which was right after 3.1 had branched so there were LOTS of changes. I'll leave this PR open for now, but unless the bug shows up in other places it's probably not worth worrying about. Here's a cut-down test case: struct QWidget { void repaint (int x, int y, int w, int h, bool erase=true); }; void foo () { typedef void (QWidget::*t14)(int, int, int, int, bool); t14 v14 = &QWidget::repaint; }
next reply other threads:[~2002-10-11 18:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-11 11:46 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-07 1:06 Eric Botcazou 2003-02-19 10:23 ebotcazou 2002-05-07 10:56 janis187
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=20021011184603.5240.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).