public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, msk@ignlabs.com, nobody@gcc.gnu.org Subject: Re: middle-end/6418: mangle.c #2199 (GCC3.04) - Emits *INTERNAL* when handling weak defined templates con- and destructors Date: Fri, 25 Oct 2002 07:34:00 -0000 [thread overview] Message-ID: <20021025143405.31342.qmail@sources.redhat.com> (raw) Synopsis: mangle.c #2199 (GCC3.04) - Emits *INTERNAL* when handling weak defined templates con- and destructors State-Changed-From-To: open->feedback State-Changed-By: bangerth State-Changed-When: Fri Oct 25 07:34:04 2002 State-Changed-Why: I cannot reproduce this problem with both gcc3.2 and mainline CVS when I follow your instructions to generate a file that shows the problem. Can you please try a newer version of gcc,and if it still fails, please provide a complete testcase. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6418
next reply other threads:[~2002-10-25 14:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-25 7:34 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-21 7:10 bangerth 2002-11-21 6:53 Michael Skriver 2002-04-23 4:56 msk
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=20021025143405.31342.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=msk@ignlabs.com \ --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).