public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net> 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: Fri, 11 Oct 2002 13:06:00 -0000 [thread overview] Message-ID: <20021011200601.2529.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1060 bytes --] The following reply was made to PR c++/7828; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: Pop Sébastian <pop@gauvain.u-strasbg.fr> Cc: austern@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/7828: g++ 3.3: bad non-lvalue error (non_cast_lvalue_or_else) Date: 11 Oct 2002 21:58:10 +0200 Pop Sébastian <pop@gauvain.u-strasbg.fr> writes: | On Wed, Oct 09, 2002 at 01:39:28AM +0200, Gabriel Dos Reis wrote: | > Pop Sébastian <pop@gauvain.u-strasbg.fr> writes: | > | > | 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) | > | > Indeed, it was fixed by Matt -- I can't recall off hand when, | > certainly somewhere in September. | > | > -- Gaby | | Maybe the following? Well, it appears that that ChangeLog entry is present on mainline but not on branch. I've moved it into the appropriate files. Matt did you also fix the bug on the 3.2 branch? -- Gaby
next reply other threads:[~2002-10-11 20:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-11 13:06 Gabriel Dos Reis [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 12:59 gdr 2002-10-08 16:56 Pop Sébastian 2002-10-08 16:46 Gabriel Dos Reis 2002-10-08 16:26 Pop Sébastian 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=20021011200601.2529.qmail@sources.redhat.com \ --to=gdr@integrable-solutions.net \ --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: 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).