From: Segher Boessenkool <segher@kernel.crashing.org>
To: Scott Wood <oss@buserror.net>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
kbuild-all@lists.01.org, "kernel test robot" <lkp@intel.com>,
"Brian Cain" <bcain@codeaurora.org>,
"Alan Modra" <amodra@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
"Fāng-ruì Sòng" <maskray@google.com>,
"Nathan Chancellor" <natechancellor@gmail.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Error: invalid switch -me200
Date: Mon, 16 Nov 2020 14:47:46 -0600 [thread overview]
Message-ID: <20201116204746.GC2672@gate.crashing.org> (raw)
In-Reply-To: <e19e3a9f47c988b30a19316ee3de2b588e20a641.camel@buserror.net>
On Mon, Nov 16, 2020 at 02:27:12PM -0600, Scott Wood wrote:
> On Fri, 2020-11-13 at 18:50 -0600, Segher Boessenkool wrote:
> > All the others work fine (and are needed afaics), it is only -me200 that
> > doesn't exist (in mainline binutils). Perhaps -me5500 will work for it
> > instead.
>
> According to Wikipedia e200 is from mpc55xx (for which I don't see any
> platform support having ever been added). e5500 is completely different (64-
> bit version of e500mc).
Ah yes, confusing processor numbers :-( That explains, sorry.
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Scott Wood <oss@buserror.net>
Cc: "Fāng-ruì Sòng" <maskray@google.com>,
"Arnd Bergmann" <arnd@kernel.org>,
kbuild-all@lists.01.org, "kernel test robot" <lkp@intel.com>,
"Brian Cain" <bcain@codeaurora.org>,
"Alan Modra" <amodra@gmail.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
"Nathan Chancellor" <natechancellor@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Error: invalid switch -me200
Date: Mon, 16 Nov 2020 14:47:46 -0600 [thread overview]
Message-ID: <20201116204746.GC2672@gate.crashing.org> (raw)
In-Reply-To: <e19e3a9f47c988b30a19316ee3de2b588e20a641.camel@buserror.net>
On Mon, Nov 16, 2020 at 02:27:12PM -0600, Scott Wood wrote:
> On Fri, 2020-11-13 at 18:50 -0600, Segher Boessenkool wrote:
> > All the others work fine (and are needed afaics), it is only -me200 that
> > doesn't exist (in mainline binutils). Perhaps -me5500 will work for it
> > instead.
>
> According to Wikipedia e200 is from mpc55xx (for which I don't see any
> platform support having ever been added). e5500 is completely different (64-
> bit version of e500mc).
Ah yes, confusing processor numbers :-( That explains, sorry.
Segher
next prev parent reply other threads:[~2020-11-16 20:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 3:21 Error: invalid switch -me200 kernel test robot
2020-11-13 3:21 ` kernel test robot
2020-11-13 17:28 ` Fāng-ruì Sòng
2020-11-13 17:28 ` Fāng-ruì Sòng
2020-11-13 19:08 ` Nathan Chancellor
2020-11-13 19:08 ` Nathan Chancellor
2020-11-13 19:42 ` Nick Desaulniers
2020-11-13 19:42 ` Nick Desaulniers
2020-11-13 19:42 ` Nick Desaulniers
2020-11-13 20:04 ` Nathan Chancellor
2020-11-13 20:04 ` Nathan Chancellor
2020-11-13 20:04 ` Nathan Chancellor
2020-11-13 20:14 ` Nick Desaulniers
2020-11-13 20:14 ` Nick Desaulniers
2020-11-13 20:14 ` Nick Desaulniers
2020-11-14 0:20 ` Segher Boessenkool
2020-11-14 0:20 ` Segher Boessenkool
2020-11-14 0:37 ` Fāng-ruì Sòng
2020-11-14 0:37 ` Fāng-ruì Sòng
2020-11-14 0:37 ` Fāng-ruì Sòng
2020-11-14 0:50 ` Segher Boessenkool
2020-11-14 0:50 ` Segher Boessenkool
2020-11-16 20:27 ` Scott Wood
2020-11-16 20:27 ` Scott Wood
2020-11-16 20:27 ` Scott Wood
2020-11-16 20:47 ` Segher Boessenkool [this message]
2020-11-16 20:47 ` Segher Boessenkool
2020-11-16 23:59 ` Alan Modra
2020-11-16 23:59 ` Alan Modra
2020-11-16 23:59 ` Alan Modra
2020-11-14 9:02 ` Christophe Leroy
2020-11-14 9:02 ` Christophe Leroy
2020-11-14 9:02 ` Christophe Leroy
2020-11-16 6:06 ` Michael Ellerman
2020-11-16 6:06 ` Michael Ellerman
2020-11-16 6:06 ` Michael Ellerman
2020-11-16 15:26 ` Christophe Leroy
2020-11-16 15:26 ` Christophe Leroy
2020-11-16 15:26 ` Christophe Leroy
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 8:48 kernel test robot
2020-10-02 8:48 ` kernel test robot
2020-07-29 16:50 kernel test robot
2020-07-29 16:50 ` kernel test robot
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=20201116204746.GC2672@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amodra@gmail.com \
--cc=arnd@kernel.org \
--cc=bcain@codeaurora.org \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=oss@buserror.net \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.