public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andris Pavenis <pavenis@lanet.lv>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7807: g++ 3.2 Fails to compile legal code that compiled OK with g++ 3.1
Date: Mon, 02 Sep 2002 08:06:00 -0000 [thread overview]
Message-ID: <20020902150601.5297.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/7807; it has been noted by GNATS.
From: Andris Pavenis <pavenis@lanet.lv>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
anthony@anthonyw.cjb.net, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/7807: g++ 3.2 Fails to compile legal code that compiled OK
with g++ 3.1
Date: Mon, 02 Sep 2002 17:56:30 +0300
Reproduced under Linux.
Looks the same as PR#7648 I reported about 2 weeks ago (for i386-slackware-linux and
i586-pc-msdosdjgpp).
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7648
Andris
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7807
next reply other threads:[~2002-09-02 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 8:06 Andris Pavenis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 12:41 mmitchel
2002-09-28 22:56 Pop Sébastian
2002-09-13 13:35 nathan
2002-09-02 2:36 anthony
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=20020902150601.5297.qmail@sources.redhat.com \
--to=pavenis@lanet.lv \
--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: link
Be 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).