public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, philipp.bachmann@obtree.com, rodrigc@gcc.gnu.org Subject: Re: c++/3136: Misleading error message / Bug? Date: Fri, 15 Jun 2001 16:20:00 -0000 [thread overview] Message-ID: <20010615232020.3430.qmail@sourceware.cygnus.com> (raw) Synopsis: Misleading error message / Bug? State-Changed-From-To: feedback->open State-Changed-By: rodrigc State-Changed-When: Fri Jun 15 16:20:20 2001 State-Changed-Why: Received test case. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3136&database=gcc
next reply other threads:[~2001-06-15 16:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-15 16:20 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-15 16:35 rodrigc 2001-06-14 18:55 rodrigc 2001-06-12 6:16 philipp.bachmann
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=20010615232020.3430.qmail@sourceware.cygnus.com \ --to=rodrigc@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=philipp.bachmann@obtree.com \ /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).