public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthew Fortune <Matthew.Fortune@imgtec.com>
To: Steve Ellcey <Steve.Ellcey@imgtec.com>,
	"gcc-patches@gcc.gnu.org"	<gcc-patches@gcc.gnu.org>
Cc: "clm@codesourcery.com" <clm@codesourcery.com>
Subject: RE: [Patch, MIPS] Change mips4 default processor to r10K
Date: Tue, 28 Apr 2015 18:40:00 -0000	[thread overview]
Message-ID: <6D39441BF12EF246A7ABCE6654B023532104261F@LEMAIL01.le.imgtec.org> (raw)
In-Reply-To: <38edc2c5-12d6-4617-b78c-77bcd77be7e7@BAMAIL02.ba.imgtec.org>

Steve Ellcey  <sellcey@imgtec.com> writes:
> This patch changes the default processor for mips4 from the r8000 to
> the
> r10000.  There are several reasons for this change, the main one
> being the difference in the r8000 madd instruction and the rest of the
> mips4
> family.  The r8000 has a fused madd instruction (no truncation between
> the
> multiply and add) but the rest of the mips4 CPUs have unfused madd
> instructions where truncation is done and the result is identical to
> using
> separate multiply and add instructions.
> 
> I plan to submit a patch later to clean up MIPS handling of madd and
> other
> fma style instructions but to do that it is necessary to do different
> things
> for r8000 vs the other mips4 targets and that is easier if r8000 is not
> the
> default processor selected when -mips4 is used.
> 
> I have also been told that very few r8000 machines were ever released
> and
> that the r10k/r12k/etc. series is probably the most common mips4
> machines
> still out there and so would be a better default.
> 
> This patch will have no affect on compiles where a specific processor
> is
> specified (i.e. -march=r80000, -march=r10000), but only when using the
> more generic -mips4 or -march=mips4 flags.  The only visible difference
> in that case is that GCC will use the r10k instruction scheduler
> instead
> of the generic MIPS scheduler (there is no r8000 specific scheduler)
> and
> that should be a good thing for most mips4 machines.
> 
> Tested with the mips-linux-gnu toolchain.
> 
> OK for checkin?
> 
> Steve Ellcey
> sellcey@imgtec.com
> 
> 
> 2015-04-28  Steve Ellcey  <sellcey@imgtec.com>
> 
> 	* config/mips/mips-cpus.def: (mips4): Change default processor
> 	from PROCESSOR_R8000 to PROCESSOR_R10000.

Ok with me. I'd like Catherine to have the chance to raise any concerns
though.

Thanks,
Matthew

  reply	other threads:[~2015-04-28 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 17:54 Steve Ellcey 
2015-04-28 18:40 ` Matthew Fortune [this message]
2015-04-29 21:15   ` Moore, Catherine

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=6D39441BF12EF246A7ABCE6654B023532104261F@LEMAIL01.le.imgtec.org \
    --to=matthew.fortune@imgtec.com \
    --cc=Steve.Ellcey@imgtec.com \
    --cc=clm@codesourcery.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).