public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
	linux-am33-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [Linux-am33-list] Re: Compiler for mn10300?
Date: Fri, 15 Feb 2008 08:49:06 +0000	[thread overview]
Message-ID: <47B55202.2090304@redhat.com> (raw)
In-Reply-To: <20080214201237.GA23227@cs181133002.pp.htv.fi>

Hi Adrian,

> What are the plans regarding getting a plain upstream gcc compiling the 
> kernel?

One of the things on my plate is to get the -mno-mem-funcs patch 
contributed upstream.  (Along with a lot of other pending AM33 patches, 
such as the support for the AM34 processor).  As it happens MEI have 
just opened an issue with regard to -mno-mem-funcs, so any pushing of 
the patch will have to wait until that is resolved.

Cheers
   Nick



      reply	other threads:[~2008-02-15  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 19:59 Compiler for mn10300? Adrian Bunk
2008-02-13 23:13 ` David Howells
2008-02-14 20:12   ` Adrian Bunk
2008-02-15  8:49     ` Nick Clifton [this message]

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=47B55202.2090304@redhat.com \
    --to=nickc@redhat.com \
    --cc=bunk@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-am33-list@redhat.com \
    --cc=linux-kernel@vger.kernel.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