public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32285] [4.1 Regression] Miscompilation with pure _Complex returning call inside another fn's argument list
Date: Thu, 14 Jun 2007 08:03:00 -0000	[thread overview]
Message-ID: <20070614080346.21673.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32285-87@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from jakub at gcc dot gnu dot org  2007-06-14 08:03 -------
Yes, I mean performance and size regressions.  But your changes to tree-nrv
never mentioned you found bugs in it and therefore are making NRV more strict,
on the contrary, PR25505 was fixing a performance/size issue where NRV was
too strict and your patch was meant to make it less strict, at least that's
what I understood from the gcc-patches thread.


-- 


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


  parent reply	other threads:[~2007-06-14  8:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 15:37 [Bug middle-end/32285] New: " jakub at gcc dot gnu dot org
2007-06-11 15:44 ` [Bug middle-end/32285] " jakub at gcc dot gnu dot org
2007-06-11 16:06 ` jconner at apple dot com
2007-06-11 18:36 ` pinskia at gcc dot gnu dot org
2007-06-11 18:59 ` jconner at apple dot com
2007-06-12 10:05 ` rguenth at gcc dot gnu dot org
2007-06-13 15:23 ` jakub at gcc dot gnu dot org
2007-06-13 17:10 ` jconner at apple dot com
2007-06-14  8:03 ` jakub at gcc dot gnu dot org [this message]
2007-06-15  8:50 ` jakub at gcc dot gnu dot org
2007-06-15 11:28 ` jakub at gcc dot gnu dot org
2007-06-20  6:36 ` jakub at gcc dot gnu dot org
2007-06-20  6:44 ` jakub at gcc dot gnu dot org
2007-06-20  6:50 ` jakub at gcc dot gnu dot org
2007-06-20  9:24 ` jakub 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=20070614080346.21673.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).