public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7145: [PATCH] g++ -O with structure initializer & return value optimization generates bad code
Date: Fri, 05 Jul 2002 08:06:00 -0000	[thread overview]
Message-ID: <20020705150603.13751.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/7145; it has been noted by GNATS.

From: "H. J. Lu" <hjl@lucon.org>
To: Jason Merrill <jason@redhat.com>
Cc: tlb@tlb.org, gcc-gnats@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: optimization/7145: [PATCH] g++ -O with structure initializer & return value optimization generates bad code
Date: Fri, 5 Jul 2002 08:01:37 -0700

 On Fri, Jul 05, 2002 at 03:59:53PM +0100, Jason Merrill wrote:
 > Here's the patch I'm applying.
 > 
 > 2002-07-05  Jason Merrill  <jason@redhat.com>
 > 
 > 	* tree.c (cp_copy_res_decl_for_inlining): Also copy DECL_INITIAL.
 > 
 
 Thanks. I assume you will also fix the same regression in gcc 3.1.
 
 
 H.J.


             reply	other threads:[~2002-07-05 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-05  8:06 H. J. Lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-05  8:06 Jason Merrill

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=20020705150603.13751.qmail@sources.redhat.com \
    --to=hjl@lucon.org \
    --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).