Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: gcc-patches@gcc.gnu.org
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: -march=r10000 Support for MIPS Targets (Old 3.4.x Patch; requires porting, assistance requested)
Date: Tue, 28 Jun 2005 00:59:59 -0400	[thread overview]
Message-ID: <42C0D94F.3030809@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]

Hi All,

I've poked around on this patch to gcc-3.4.x from time-to-time (When I get the 
time to do so), and haven't really gotten anywhere.  It's a patch I 
forward-ported some time ago from gcc-3.0 up to gcc-3.4.2/3.4.3.  It's worked 
fine in gcc-3.4.3 on MIPS userlands under IP28, IP30, and IP27 systems for 
several months now (probably closer to a year at this point).  Based on feedback 
I've gotten from Eric Christopher back in Aug '04 (Hi Eric) the patch itself 
looks sane, and with me and multiple users running it, it's not had any reported 
problems thus far, so I consider it stable enough to try and submit it in its 
current 3.4.x form to this list.

The downside is, with everyone moving to 4.x series now, 3.4.x isn't going to be 
around much longer.  I'm not much of a compiler guru, so with the massive 
changes between 3.4.x and 4.x's mips.md format (and deprecating 
define_function_insn and splitting of mips.md to cpu-specific md's), most of my 
ability to analyze and port changes is vastly reduced (since I usually look for 
similarities in code and adjust accordingly).

If at all possible I'd like to see it make it into gcc at some point in time, 
not necessarily gcc-4.1, as the patch as it currently stands needs someone to do 
the work of porting it to fit into 4.x, but I figure if I keep holding onto it, 
it'll be gcc-5.x before this thing ever gets anywheres.

So if anyone wants to take a stab at porting it, I'd be interested to see the 
results (so I can compare it to 3.4.x and maybe get an idea of how the changes 
really port over to 4.x).

For historical reference, the original patch was submitted for gcc-3.0 back in 
July 2001, and can be seen here:
http://gcc.gnu.org/ml/gcc-patches/2001-07/msg01161.html



--Kumba

-- 
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

[-- Attachment #2: gcc-3.4.x-mips-add-march-r10k.patch.gz --]
[-- Type: application/x-gzip, Size: 2850 bytes --]

             reply	other threads:[~2005-06-28  4:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28  4:59 Kumba [this message]
2005-06-28  8:07 ` -march=r10000 Support for MIPS Targets (Old 3.4.x Patch; requires porting, assistance requested) Steven Bosscher
2005-07-01  4:51   ` Kumba
2005-07-03  2:17     ` 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=42C0D94F.3030809@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linux-mips@linux-mips.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