public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rdsandiford@googlemail.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] MIPS/GAS: Disable branch relaxation for BPOSGE32/64
Date: Sat, 26 Feb 2011 09:38:00 -0000	[thread overview]
Message-ID: <87hbbrqgog.fsf@firetop.home> (raw)
In-Reply-To: <alpine.DEB.1.10.1102212039440.20460@tp.orcam.me.uk> (Maciej	W. Rozycki's message of "Fri, 25 Feb 2011 00:57:38 +0000 (GMT)")

"Maciej W. Rozycki" <macro@codesourcery.com> writes:
>  Here's a change to disable branch relaxation for the BPOSGE32 and 
> BPOSGE64 MIPS DSP instructions.  They have no complementing branches and 
> therefore cannot be relaxed using our current infrastructure -- an extra 
> unconditional branch over the long jump would have to be produced and I 
> think there's little demand for such a feature, hence my simple change.  

Agreed.

> 2011-02-21  Maciej W. Rozycki  <macro@codesourcery.com>
>
> 	gas/
> 	* config/tc-mips.c (append_insn): Disable branch relaxation for
> 	DSP instructions.
>
> 	gas/testsuite/
> 	* gas/mips/relax-bposge.l: New test for DSP branch relaxation.
> 	* gas/mips/relax-bposge.s: Source for the new test.
> 	* gas/mips/mips.exp: Run the new test.

OK.

For the record, I wasn't sure at first whether keying off ISA_DSP* was
conceptually a good idea, because there doesn't seem to be anything
inherent in the DSP extensions that would prevent complementing branches
from being defined in DSPr3.  Of course, if that happened, the change is
still conservatively correct.  We'd just lack a potential feature for
those branches.  But I was wondering whether it would be better to have
a separate flag for branches without complements.

I agree that that's probably overkill as things stand though.
If we ever need to use the condition elsewhere, or if more branches
of this kind are added, then we can add a separate flag at that stage.

Thanks,
Richard

  reply	other threads:[~2011-02-26  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  0:57 Maciej W. Rozycki
2011-02-26  9:38 ` Richard Sandiford [this message]
2011-02-28 16:30   ` Maciej W. Rozycki

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=87hbbrqgog.fsf@firetop.home \
    --to=rdsandiford@googlemail.com \
    --cc=binutils@sourceware.org \
    --cc=macro@codesourcery.com \
    /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).