From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix up adjust_return_value_with_ops (PR tree-optimization/56539)
Date: Thu, 07 Mar 2013 16:38:00 -0000 [thread overview]
Message-ID: <5138C28A.2020108@redhat.com> (raw)
In-Reply-To: <20130306232819.GY12913@tucnak.redhat.com>
On 03/06/2013 04:28 PM, Jakub Jelinek wrote:
> On Wed, Mar 06, 2013 at 03:00:49PM -0700, Jeff Law wrote:
>> Doesn't the code in update_accumulator_with_ops need the same
>> change?
>
> No, the difference is that it uses false as the next to last argument,
> i.e. inserts after gsi, in which case GSI_CONTINUE_LINKING is desirable,
> so that the stmt is inserted after that.
Thanks. Just wanted to make sure -- I've never had to ponder how the
GSI/BSI linking code works much.
Jeff
prev parent reply other threads:[~2013-03-07 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 16:43 Jakub Jelinek
2013-03-06 22:00 ` Jeff Law
2013-03-06 23:28 ` Jakub Jelinek
2013-03-07 16:38 ` Jeff Law [this message]
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=5138C28A.2020108@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).