public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Nathan Chancellor" <natechancellor@gmail.com>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Brian Cain" <bcain@codeaurora.org>,
	"Fāng-ruì Sòng" <maskray@google.com>,
	"kernel test robot" <lkp@intel.com>,
	kbuild-all@lists.01.org,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>
Subject: Re: Error: invalid switch -me200
Date: Fri, 13 Nov 2020 18:20:37 -0600	[thread overview]
Message-ID: <20201114002037.GW2672@gate.crashing.org> (raw)
In-Reply-To: <CAKwvOdkBSGPaKmQY1nERVe4_n19Q=MUtuwdond=FJAAF9N9Zhg@mail.gmail.com>

On Fri, Nov 13, 2020 at 12:14:18PM -0800, Nick Desaulniers wrote:
> > > > Error: invalid switch -me200
> > > > Error: unrecognized option -me200
> > >
> > > 251 cpu-as-$(CONFIG_E200)   += -Wa,-me200
> > >
> > > Are those all broken configs, or is Kconfig messed up such that
> > > randconfig can select these when it should not?
> >
> > Hmmm, looks like this flag does not exist in mainline binutils? There is
> > a thread in 2010 about this that Segher commented on:
> >
> > https://lore.kernel.org/linuxppc-dev/9859E645-954D-4D07-8003-FFCD2391AB6E@kernel.crashing.org/
> >
> > Guess this config should be eliminated?

The help text for this config options says that e200 is used in 55xx,
and there *is* an -me5500 GAS flag (which probably does this same
thing, too).  But is any of this tested, or useful, or wanted?

Maybe Christophe knows, cc:ed.


Segher

  reply	other threads:[~2020-11-14  0:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  3:21 Error: invalid switch -me200 kernel test robot
2020-11-13 17:28 ` Fāng-ruì Sòng
2020-11-13 19:08   ` Nathan Chancellor
2020-11-13 19:42     ` Nick Desaulniers
2020-11-13 20:04       ` Nathan Chancellor
2020-11-13 20:14         ` Nick Desaulniers
2020-11-14  0:20           ` Segher Boessenkool [this message]
2020-11-14  0:37             ` Fāng-ruì Sòng
2020-11-14  0:50               ` Segher Boessenkool
2020-11-16 20:27                 ` Scott Wood
2020-11-16 20:47                   ` Segher Boessenkool
2020-11-16 23:59                 ` Alan Modra
2020-11-14  9:02             ` Christophe Leroy
2020-11-16  6:06               ` Michael Ellerman
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-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=20201114002037.GW2672@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@kernel.org \
    --cc=bcain@codeaurora.org \
    --cc=christophe.leroy@csgroup.eu \
    --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=mpe@ellerman.id.au \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox