public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: nobody@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: Mon, 09 Sep 2002 13:56:00 -0000	[thread overview]
Message-ID: <20020909205601.16664.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7828; it has been noted by GNATS.

From: Nathan Sidwell <nathan@codesourcery.com>
To: snyder@fnal.gov, gcc-gnats@gcc.gnu.org, pcarlini@unitus.it,
   gcc-bugs@gcc.gnu.org, Matt Austern <austern@apple.com>,
   Andrew Pinski
 <pinskia@physics.uc.edu>
Cc: mark@codesourcery.com
Subject: Re: c++/7828: g++ 3.3: bad non-lvalue error (non_cast_lvalue_or_else)
Date: Mon, 09 Sep 2002 21:54:58 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7828
 
 Paolo asked me to look at this and 7858.
 
 <really short version>
 Scott is usually right about c++
 
 <short version>
 Scott's code is well formed, g++ is wrong, Matt's patch probably broke it.
 
 <long version>
 	long (x)
 is an rvalue [5.2.3]/2
 	Foo (const long &)
 can bind to an rvalue [5.2.2]/4, [8.5]/12, [8.5.3]/5 2nd major point
 	'Otherwise the reference shall be to a non-volatile const type' ...
 	'otherwise a temporary of type 'cv1 T1' is created ...'
 
 Matt, as it appears that your patch has broken this, even though it might
 have fixed some bug, could you either fix the latent bug, or revert your patch
 (like the development plan specifies). It'd be neat to add a scott's code as
 a g++ testcase too.
 
 nathan
 


             reply	other threads:[~2002-09-09 20:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 13:56 Nathan Sidwell [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-10-08 16:26 Pop Sébastian
2002-09-13  9:42 nathan
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=20020909205601.16664.qmail@sources.redhat.com \
    --to=nathan@codesourcery.com \
    --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).