public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr>
To: austern@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7828: g++ 3.3: bad non-lvalue error (non_cast_lvalue_or_else)
Date: Tue, 08 Oct 2002 16:26:00 -0000 [thread overview]
Message-ID: <20021008232601.10410.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/7828; it has been noted by GNATS.
From: =?iso-8859-1?Q?Pop_S=E9bastian?= <pop@gauvain.u-strasbg.fr>
To: nathan@gcc.gnu.org, austern@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, snyder@fnal.gov,
gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/7828: g++ 3.3: bad non-lvalue error (non_cast_lvalue_or_else)
Date: Wed, 9 Oct 2002 01:24:56 +0200
On Fri, Sep 13, 2002 at 04:42:37PM -0000, nathan@gcc.gnu.org wrote:
> Synopsis: g++ 3.3: bad non-lvalue error (non_cast_lvalue_or_else)
>
> Responsible-Changed-From-To: unassigned->austern
> Responsible-Changed-By: nathan
> Responsible-Changed-When: Fri Sep 13 09:42:37 2002
> Responsible-Changed-Why:
> patching
> State-Changed-From-To: open->analyzed
> State-Changed-By: nathan
> State-Changed-When: Fri Sep 13 09:42:37 2002
> State-Changed-Why:
> confirmed
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7828
I cannot reproduce the error with
gcc version 3.2.1 20020924 (Debian prerelease)
nor with the last cvs:
version gcc 3.3 20021007 (experimental)
next reply other threads:[~2002-10-08 23:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 16:26 Pop Sébastian [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-11 13:26 Gabriel Dos Reis
2002-10-11 13:16 Matt Austern
2002-10-11 13:06 Gabriel Dos Reis
2002-10-11 12:59 gdr
2002-10-08 16:56 Pop Sébastian
2002-10-08 16:46 Gabriel Dos Reis
2002-09-13 9:42 nathan
2002-09-09 13:56 Nathan Sidwell
2002-09-05 9:26 Scott Snyder
2002-09-04 12:26 Andrew Pinski
2002-09-04 12:06 snyder
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=20021008232601.10410.qmail@sources.redhat.com \
--to=pop@gauvain.u-strasbg.fr \
--cc=austern@gcc.gnu.org \
--cc=gcc-prs@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).