From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>, <kbuild-all@01.org>,
Paul Burton <paul.burton@imgtec.com>,
<linux-kernel@vger.kernel.org>, Philip Li <philip.li@intel.com>
Subject: Re: [kbuild-all] mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal'
Date: Thu, 21 Apr 2016 22:10:51 +0100 [thread overview]
Message-ID: <alpine.DEB.2.00.1604212159440.21846@tp.orcam.me.uk> (raw)
In-Reply-To: <20160421203415.GK24051@linux-mips.org>
On Thu, 21 Apr 2016, Ralf Baechle wrote:
> > I don't think it makes sense as the compiler won't support MIPSr6 code
> > anyway, so first it'll bail out on `-march=mips32r6', and if we go even
> > further and disable that too, then GAS will probably break somewhere on
> > inline asm and GCC will produce code which does not make sense otherwise.
>
> GCC 5.2.0 claims to support mips32r6 and mips64r6. It's just the option
> -mcompact-branches which seem to have been added later only.
Ah, I see -- I didn't track the timeline of support for this compiler's
option and I took it from an earlier response that the compiler does not
support R6 at all.
In that case however it looks to me like these `-mcompact-branches='
options (all the three we support) need to be wrapped into `$(call
cc-option,...)'. They do not affect any functionality and they are an
optimisation choice only anyway (and therefore I wonder why they've been
placed in arch/mips/Kconfig.debug rather than arch/mips/Kconfig).
Maciej
next prev parent reply other threads:[~2016-04-21 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 5:44 mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal' kbuild test robot
2016-04-20 13:30 ` Ralf Baechle
2016-04-21 4:51 ` [kbuild-all] " Fengguang Wu
2016-04-21 19:55 ` Maciej W. Rozycki
2016-04-21 20:34 ` Ralf Baechle
2016-04-21 21:10 ` Maciej W. Rozycki [this message]
2016-04-22 8:54 ` Paul Burton
2016-04-22 15:48 ` Maciej W. Rozycki
2016-04-21 20:31 ` Ralf Baechle
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=alpine.DEB.2.00.1604212159440.21846@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.burton@imgtec.com \
--cc=philip.li@intel.com \
--cc=ralf@linux-mips.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.