public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19199] [3.3/3.4/4.0/4.1 Regression] Wrong warning about returning a reference to a temporary
Date: Mon, 07 Mar 2005 04:19:00 -0000	[thread overview]
Message-ID: <20050307041915.1101.qmail@sourceware.org> (raw)
In-Reply-To: <20041230105911.19199.lars@trolltech.com>


------- Additional Comments From mark at codesourcery dot com  2005-03-07 04:19 -------
Subject: Re: [PR c++/19199] don't turn cond_expr lvalue into min_expr rvalue
 (continued from PR c++/20280)

Alexandre Oliva wrote:
> On Mar  5, 2005, Mark Mitchell <mark@codesourcery.com> wrote:
> 
> 
>>Roger has objected to this change in the past.  As I noted in the
>>audit trail for 19199, there's stuff in build_modify_expr to handle
>>MIN_EXPR/MAX_EXPR as lvalues
> 
> 
> Problem is, with the transformation performed by fold, it's no longer
> an lvalue, and forcing it back into an lvalue just because it looks
> like it should be one could break other programs.

Yes, I understand.  You still need to take it up with Roger, though.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19199


  parent reply	other threads:[~2005-03-07  4:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 10:59 [Bug c++/19199] New: " lars at trolltech dot com
2004-12-30 14:49 ` [Bug c++/19199] [3.3/3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-31 12:45 ` steven at gcc dot gnu dot org
2004-12-31 14:51 ` pinskia at gcc dot gnu dot org
2005-01-01  0:21 ` rth at gcc dot gnu dot org
2005-01-02  0:43 ` gdr at integrable-solutions dot net
2005-01-07  1:11 ` pinskia at gcc dot gnu dot org
2005-01-07  8:09 ` mmitchel at gcc dot gnu dot org
2005-01-09  4:46 ` rth at gcc dot gnu dot org
2005-01-26 18:02 ` amylaar at gcc dot gnu dot org
2005-01-27 23:08 ` amylaar at gcc dot gnu dot org
2005-03-04  8:13 ` [Bug c++/19199] [3.3/3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-03-04 19:08 ` aoliva at redhat dot com
2005-03-06  0:14 ` mark at codesourcery dot com
2005-03-07  3:28 ` aoliva at redhat dot com
2005-03-07  4:19 ` mark at codesourcery dot com [this message]
2005-03-08 23:23 ` aoliva at redhat dot com
2005-03-09  1:29 ` roger at eyesopen dot com
2005-03-09  4:11 ` aoliva at redhat dot com
2005-03-25  6:04 ` roger at eyesopen dot com
2005-03-25  6:29 ` mark at codesourcery dot com
2005-03-30  2:55 ` aoliva at gcc dot gnu dot org
2005-03-30  7:20 ` mark at codesourcery dot com
2005-04-02 17:29 ` aoliva at redhat dot com
2005-04-03  3:20 ` roger at eyesopen dot com
2005-04-04  0:37 ` mark at codesourcery dot com
2005-04-04  5:02 ` cvs-commit at gcc dot gnu dot org
2005-04-04 13:32 ` aoliva at redhat dot com
2005-04-04 13:41 ` joseph at codesourcery dot com
2005-04-04 13:51 ` aoliva at redhat dot com
2005-04-04 15:03 ` aoliva at redhat dot com
2005-04-04 16:02 ` roger at eyesopen dot com
2005-04-04 16:40 ` mark at codesourcery dot com
2005-04-04 20:18 ` [Bug c++/19199] [3.3/3.4/4.0 " aoliva at redhat dot com
2005-04-04 23:01 ` mark at codesourcery dot com
2005-04-05  5:16 ` cvs-commit at gcc dot gnu dot org
2005-04-05 23:14 ` [Bug c++/19199] [3.3/3.4 " roger at eyesopen dot com
2005-04-05 23:49 ` mark at codesourcery dot com
2005-04-06  0:04 ` roger at eyesopen dot com
2005-04-29 18:28 ` mmitchel at gcc dot gnu dot org

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=20050307041915.1101.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).