From: Alan Swanson <swanson@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Binutils bug on not using NOPL with i686 needs persuasive arguments
Date: Mon, 13 Oct 2008 15:34:09 +0100 [thread overview]
Message-ID: <20081013143409.GA10924@zaphod.infiniteimprobability.net> (raw)
Hi. (Usual not subscribed CC request.)
I need some heavyweight assistance with verifying and convincing the
binutils gas maintainer that using NOPL on i686 is undesirable and also
fixing it so that only march changes the NOP sequence used and not
mtune.
This was from from thread "[BUG] x86 kenel won't boot under Virtual PC"
where NOPL was deemed rather bad and a bug requested. I was
investigating a Geode miniitx motherboard and it was still an issue
with no bug was raised so did so.
http://marc.info/?l=linux-kernel&m=122090041613423&w=2
http://sourceware.org/bugzilla/show_bug.cgi?id=6957
MARCH VERSUS MTUNE
The bug was closed as works for me but the patch that was applied
doesn't seem to change anything in regards mtune versus march
selection, though the testcase result is correct. However I'm worried
it now means passing -march=i686 will start using NOPL and break
things that were conviently missed by gcc stripping the mtune option
passed to gas. Which leads to...
NO NOPL WITH I686
Though pretty unlikely and just being standards strict, as an Intel
employee there may be a possible self-interest and makes it harder
convincing him that that NOPL is undesirable with -march=i686 even
if an original standard. From comment 10 I don't see how using
f32_patt will prevent the assembler taking SSE instructions by
default but I don't have the knowledge to argue that point.
--
Thanks, Alan.
reply other threads:[~2008-10-13 14:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081013143409.GA10924@zaphod.infiniteimprobability.net \
--to=swanson@ukfsn.org \
--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