public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9778 -- causing patch Date: Thu, 20 Feb 2003 23:46:00 -0000 [thread overview] Message-ID: <20030220234601.29281.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9778; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <oldham@codesourcery.com> Cc: Subject: Re: c++/9778 -- causing patch Date: Thu, 20 Feb 2003 17:41:38 -0600 (CST) This patch > 2003-01-16 Jeffrey D. Oldham <oldham@codesourcery.com> > > * cp-tree.h (tsubst_copy_and_build): New declaration. > * pt.c (tsubst_copy): Remove 'build_expr_from_tree' from comment. > (tsubst_expr): Use 'tsubst_copy_and_build'. Update initial comment. > (tsubst_copy_and_build): New function. seems to be causing the ICE in PR 9778. A small testcase is ---------------------------- namespace NS { template <int N> void foo (); } template <int N> struct X { int m; int g () { NS::foo<sizeof(m)>(); } }; template class X<2>; --------------------------- Jeffrey, would you mind taking a look? This report seems to be the last that prevents me from building (and then testing again) my library with mainline... If you are lucky, the fix to this report also fixes PR 9749, see the comment in 9778. Thanks Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
reply other threads:[~2003-02-20 23:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030220234601.29281.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).