public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@redhat.com>
To: Richard Sandiford <rsandifo@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: Rework MIPS nop-insertion code, add -mfix-vr4130 [10/11]
Date: Tue, 08 Mar 2005 19:43:00 -0000	[thread overview]
Message-ID: <1110310989.5027.20.camel@localhost.localdomain> (raw)
In-Reply-To: <wvn3bv6cgtn.fsf_-_@talisman.cambridge.redhat.com>


> Tested on mips64{,el}-linux-gnu and mipsisa64{,el}-elf.  OK to install?
> 
> Richard
> 
> 
> 
> 	* config/tc-mips.c (append_insn): Remove cop_interlocks test from
> 	branch delay code.
> 
> testsuite/
> 	* gas/mips/relax-swap1-mips[12].d: Expect the delay slots of
> 	bc1f and bc1t to be filled.
> 	* gas/mips/branch-misc-3.[sd]: New test.
> 	* gas/mips/mips.exp: Run it.

OK mainline and branch.

-eric

  parent reply	other threads:[~2005-03-08 19:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 14:39 Rework MIPS nop-insertion code, add -mfix-vr4130 [1/11] Richard Sandiford
2005-03-08 14:42 ` Rework MIPS nop-insertion code, add -mfix-vr4130 [2/11] Richard Sandiford
2005-03-08 14:46   ` Rework MIPS nop-insertion code, add -mfix-vr4130 [3/11] Richard Sandiford
2005-03-08 14:50     ` Rework MIPS nop-insertion code, add -mfix-vr4130 [4/11] Richard Sandiford
2005-03-08 14:56       ` Rework MIPS nop-insertion code, add -mfix-vr4130 [5/11] Richard Sandiford
2005-03-08 15:00         ` Rework MIPS nop-insertion code, add -mfix-vr4130 [6/11] Richard Sandiford
2005-03-08 15:05           ` Rework MIPS nop-insertion code, add -mfix-vr4130 [7/11] Richard Sandiford
2005-03-08 15:06             ` Rework MIPS nop-insertion code, add -mfix-vr4130 [8/11] Richard Sandiford
2005-03-08 15:10               ` Rework MIPS nop-insertion code, add -mfix-vr4130 [9/11] Richard Sandiford
2005-03-08 15:12                 ` Rework MIPS nop-insertion code, add -mfix-vr4130 [10/11] Richard Sandiford
2005-03-08 15:16                   ` Rework MIPS nop-insertion code, add -mfix-vr4130 [11/11] Richard Sandiford
2005-03-08 19:45                     ` Eric Christopher
2005-03-08 19:43                   ` Eric Christopher [this message]
2005-03-08 19:42                 ` Rework MIPS nop-insertion code, add -mfix-vr4130 [9/11] Eric Christopher
2005-03-08 19:19               ` Rework MIPS nop-insertion code, add -mfix-vr4130 [8/11] Eric Christopher
2005-03-08 19:18             ` Rework MIPS nop-insertion code, add -mfix-vr4130 [7/11] Eric Christopher
2005-03-09  9:55               ` Richard Sandiford
2005-03-08 19:12           ` Rework MIPS nop-insertion code, add -mfix-vr4130 [6/11] Eric Christopher
2005-03-08 19:12         ` Rework MIPS nop-insertion code, add -mfix-vr4130 [5/11] Eric Christopher
2005-03-08 19:09       ` Rework MIPS nop-insertion code, add -mfix-vr4130 [4/11] Eric Christopher
2005-03-08 19:08     ` Rework MIPS nop-insertion code, add -mfix-vr4130 [3/11] Eric Christopher
2005-03-08 19:07   ` Rework MIPS nop-insertion code, add -mfix-vr4130 [2/11] Eric Christopher
2005-03-08 19:06 ` Rework MIPS nop-insertion code, add -mfix-vr4130 [1/11] Eric Christopher

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=1110310989.5027.20.camel@localhost.localdomain \
    --to=echristo@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=rsandifo@redhat.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).