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: c++/9820: [3.3/3.4 regression] ice in build_baselink (templates) Date: Mon, 24 Feb 2003 23:26:00 -0000 [thread overview] Message-ID: <20030224232601.3895.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9820; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: gcc-gnats@gcc.gnu.org, Janis Johnson <janis187@us.ibm.com> Subject: Re: c++/9820: [3.3/3.4 regression] ice in build_baselink (templates) Date: Mon, 24 Feb 2003 15:26:40 -0800 On Mon, Feb 24, 2003 at 05:13:26PM -0600, Wolfgang Bangerth wrote: > > Here's a smaller testcase: > ------------------------ > template <typename T> struct X { > template<typename> static int test(...); > template<typename> static int test(int *); > > static const int i = sizeof(X<T>::template test<int>(0)); > }; > > const int Yes = X<int>::i; > ------------------------ > > However, Janis, I can't seem to create a testcase that is compilable by > 3.2 and yet generates the ICE in 3.3 and 3.4. Why don't you just grep the > output of the compiler? Yes, that's what I normally do for ice-on-illegal code. If the submitter's original test case is supposed to compile successfully with earlier versions of GCC, I might end up finding a patch that's not relevant to the submitter's ICE.
next reply other threads:[~2003-02-24 23:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-24 23:26 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-11 22:51 jason 2003-03-11 20:16 jason 2003-02-25 20:46 Janis Johnson 2003-02-24 23:36 Wolfgang Bangerth 2003-02-24 23:16 Wolfgang Bangerth 2003-02-24 22:46 Janis Johnson 2003-02-24 15:27 bangerth
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=20030224232601.3895.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).