From: Steve Ellcey <sellcey@imgtec.com>
To: Bernd Schmidt <bschmidt@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] Fix bug for frame instructions in annulled delay slots
Date: Mon, 07 Dec 2015 20:43:00 -0000 [thread overview]
Message-ID: <1449520983.4788.93.camel@ubuntu-sellcey> (raw)
In-Reply-To: <5665E530.9010603@redhat.com>
On Mon, 2015-12-07 at 20:59 +0100, Bernd Schmidt wrote:
> On 12/07/2015 08:43 PM, Steve Ellcey wrote:
> > I am not sure about this. There is an earlier if statement in the loop
> > that does a 'return' instead of a break (or continue) and there is a
> > return in the 'else' part of the if that sets must_annul. Both of these
> > are inside the loop that looks at all the instructions in the sequence
> > 'seq'. I think the code is looking at all the instructions in the
> > sequence and if any of them fail one of the tests in the loop (in this
> > case require annulling) then we can't handle any of the instructions in
> > the sequence and so we return immediately without putting any of the
> > instructions from 'seq' in the delay slot. I believe a frame related
> > instruction in an annulled branch needs to be handled that way too.
>
> Ah, I think I was looking at the other function that has the same
> must_annul test (steal_delay_list_from_fallthrough). The patch is ok
> without the backslash. Maybe the other function ought to be changed as
> well though?
>
>
> Bernd
That would seem reasonable, though I don't have a test case for where
the change to that routine would actually make a difference in the
compilation. I'll create a patch and test it to make sure it doesn't
cause any problems and then submit it as a follow-up to this change.
Steve Ellcey
sellcey@imgtec.com
prev parent reply other threads:[~2015-12-07 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 18:54 Steve Ellcey
2015-12-07 19:28 ` Bernd Schmidt
2015-12-07 19:30 ` Jeff Law
2015-12-07 21:19 ` Steve Ellcey
2015-12-08 22:54 ` Jeff Law
2015-12-07 19:44 ` Steve Ellcey
2015-12-07 19:59 ` Bernd Schmidt
2015-12-07 20:43 ` Steve Ellcey [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=1449520983.4788.93.camel@ubuntu-sellcey \
--to=sellcey@imgtec.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@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).