mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Curnow <Richard.Curnow@superh.com>
To: linux-kernel@vger.kernel.org
Cc: Paul Mundt <lethal@linux-sh.org>, Dan Kegel <dank@kegel.com>,
	Sean McGoogan <sean.mcgoogan@superh.com>
Subject: Re: Kernel Cross Compiling [update]
Date: Thu, 26 Feb 2004 13:02:49 +0000	[thread overview]
Message-ID: <20040226130249.GD16667@malvern.uk.w2k.superh.com> (raw)
In-Reply-To: <20040223144149.GC4092@MAIL.13thfloor.at>

On Mon, 23 Feb, 2004 at  3:41pm, Herbert Poetzl wrote:
> On Mon, Feb 23, 2004 at 01:28:19PM +0000, Richard Curnow wrote:
> > 
> > The last public release we made of the SH-5 tools is available at
> > 
> >     ftp://ftp.uk.superh.com/pub/SuperH-GNU/Barcelona-20030414
> 
> how are they related to the 'mainline' toolchain?

This release equated to something like gcc 3.2.1 + some work from the
3.3 branch + some in-house work.

> i.e. is this something completely separate, or do you follow the
> binutils/gcc updates from time to time?

No, it's not completely separate.  We do follow the mainline tree
(largely via gcc CVS rather than released tarballs), though we tend to
have fairly long periods between such 'rebaselinings'.

> what would be the binutils/gcc version which is 'closest' to 'your'
> toolchain? wouldn't it make sense to get those changes back into the
> mainline?

A lot of changes have already gone into the mainline gcc 3.4 branch.

As for binutils, I assume the position is similar, but I've not checked
the details.

> > The SH-5 tools we're currently using in-house are a few months more
> > advanced than those.  (They date from about August 2003.)  We'd be
> > happy to package this version up and make it available if people
> > express interest in this.
> 
> sure I'm interested *expressing interest*

OK.  Acknowleged.  BTW that version has the same basic ancestry as the
April 14th version, it just has some additional in-house fixes in it.

HTH
Richard

-- 
Richard \\\ SH-4/SH-5 Core & Debug Architect
Curnow  \\\         SuperH (UK) Ltd, Bristol

  reply	other threads:[~2004-02-26 13:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  3:53 Herbert Poetzl
2004-02-22  6:02 ` Dan Kegel
2004-02-22 15:42   ` Herbert Poetzl
2004-02-22  8:43 ` Geert Uytterhoeven
2004-02-22  9:07 ` Russell King
2004-02-22 15:09   ` Herbert Poetzl
2004-02-22 12:45 ` Dr. David Alan Gilbert
2004-02-22 15:22   ` Herbert Poetzl
2004-02-22 15:52 ` Paul Mundt
2004-02-22 17:07   ` Herbert Poetzl
2004-02-22 17:23     ` Paul Mundt
2004-02-23 13:28       ` Richard Curnow
2004-02-23 14:41         ` Herbert Poetzl
2004-02-26 13:02           ` Richard Curnow [this message]
2004-02-23 19:42 ` Jim Wilson
2004-02-23 20:32   ` Herbert Poetzl
2004-02-24  1:49     ` Dan Kegel
2004-02-24  8:53       ` Herbert Poetzl
2004-02-22 16:36 Arnd Bergmann

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=20040226130249.GD16667@malvern.uk.w2k.superh.com \
    --to=richard.curnow@superh.com \
    --cc=dank@kegel.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.mcgoogan@superh.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

all inboxes | Powered by JetHome®