From: Tom Rini <trini@kernel.crashing.org>
To: Alan Modra <amodra@bigpond.net.au>
Cc: Hollis Blanchard <hollisb@us.ibm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Olaf Hering <olh@suse.de>,
Stef Simoens <stefaan.simoens@coditel.net>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] fix missing option in binutils version check
Date: Mon, 26 Jul 2004 12:36:52 -0700 [thread overview]
Message-ID: <20040726193652.GE28588@smtp.west.cox.net> (raw)
In-Reply-To: <20040725060754.GE7099@bubble.modra.org>
On Sun, Jul 25, 2004 at 03:37:54PM +0930, Alan Modra wrote:
> On Sun, Jul 04, 2004 at 11:33:31AM -0500, Hollis Blanchard wrote:
> > On Jul 4, 2004, at 3:32 AM, Geert Uytterhoeven wrote:
> > >
> > >Perhaps it makes sense to add a directive to the assembler to switch
> > >on the
> > >fly, cfr. the `.chip' directive on m68k? E.g. using
> > >
> > > .chip 68040
> > >
> > >we switch to 68040 mode, and using
> > >
> > > .chip 68k
> > >
> > >we switch back to generic mode. That way we can have instructions for
> > >different
> > >CPU types in the same kernel, while the assembler still checks the
> > >validity
> > >depending on the selected CPU type.
> >
> > That's come up before, and iirc Alan Modra said the support isn't there
> > now for PPC and is relatively low on the priority list (but is on it).
>
> Implemented 2003-11-22 for ppc. Even documented. :-)
But working in what versions of binutils ?
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-26 19:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 7:43 [PATCH] fix typo in binutils version check Olaf Hering
2004-06-05 10:40 ` Christian Kujau
2004-06-05 11:11 ` Olaf Hering
2004-06-05 13:11 ` Christian Kujau
2004-06-07 15:57 ` Tom Rini
2004-06-08 11:25 ` [PATCH] fix missing option " Olaf Hering
2004-06-10 0:16 ` Tom Rini
2004-06-14 9:15 ` Olaf Hering
2004-06-14 16:23 ` Tom Rini
2004-06-14 17:38 ` Olaf Hering
2004-06-14 18:07 ` Olaf Hering
2004-06-14 20:55 ` Tom Rini
2004-06-14 21:19 ` Olaf Hering
2004-06-15 16:12 ` Tom Rini
2004-06-15 17:25 ` Olaf Hering
2004-06-15 17:46 ` Tom Rini
2004-07-03 22:29 ` Olaf Hering
2004-07-04 1:30 ` Stef Simoens
2004-07-04 2:41 ` Tom Rini
2004-07-04 8:32 ` Geert Uytterhoeven
2004-07-04 16:33 ` Hollis Blanchard
2004-07-25 6:07 ` Alan Modra
2004-07-26 19:36 ` Tom Rini [this message]
2004-07-26 23:03 ` Alan Modra
2004-07-26 23:07 ` Tom Rini
2004-07-04 18:32 ` Tom Rini
2004-07-04 7:23 ` Olaf Hering
2004-07-05 18:32 ` Tom Rini
2004-07-09 1:34 ` Tom Rini
2004-07-09 1:43 ` Tom Rini
2004-07-12 9:06 ` Olaf Hering
2004-07-12 15:11 ` Tom Rini
2004-07-12 18:03 ` Tom Rini
2004-07-13 13:49 ` Olaf Hering
2004-07-13 14:01 ` Tom Rini
2004-07-13 14:02 ` Olaf Hering
2004-07-13 14:20 ` Tom Rini
2004-07-13 15:18 ` Olaf Hering
2004-07-13 15:26 ` Tom Rini
2004-07-13 15:29 ` Olaf Hering
2004-07-13 19:45 ` Tom Rini
2004-07-14 23:23 ` Tom Rini
2004-07-15 7:54 ` Geert Uytterhoeven
2004-07-15 12:50 ` Olaf Hering
2004-07-15 14:15 ` Tom Rini
2004-07-15 14:24 ` Olaf Hering
2004-07-15 14:23 ` Tom Rini
2004-07-05 18:18 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 16:19 Christian
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=20040726193652.GE28588@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=amodra@bigpond.net.au \
--cc=geert@linux-m68k.org \
--cc=hollisb@us.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=olh@suse.de \
--cc=stefaan.simoens@coditel.net \
/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 NNTP newsgroup(s).