public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org,
	Quentin Neill <quentin.neill.gnu@gmail.com>,
	       Andreas Schwab <aschwab@redhat.com>
Subject: Re: [rfc] nopl should not be output on -mtune=i686
Date: Tue, 08 Feb 2011 19:01:00 -0000	[thread overview]
Message-ID: <20110208190117.GA12119@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTinaVf-tOcsLu1dO8aGvneJkoSUFCWGNF-=EKp78@mail.gmail.com>

On Tue, 08 Feb 2011 18:23:35 +0100, H.J. Lu wrote:
> On Tue, Feb 8, 2011 at 9:10 AM, Jan Kratochvil
> <jan.kratochvil@redhat.com> wrote:
> > Current binutils HEAD:
> > -march | -mtune  | nopl used?  | after the attached patch: nopl used?
> >  -    |   -     |    no       | no
> >  i686  | -/i686  |    no       | no
> >  -    |   i686  |   yes = BUG | no
> >  core2 | -/core2 |   yes       | yes
> >  -    |   core2 |   yes = BUG | no
> >
> > => Currently suppressing -march now produces more advanced code output, this
> >   does not seem correct to me.
> 
> By default, x86 assembler assumes that the target processor accepts
> any instructions.  You can restrict ISA sets by -march and .arch directive.

Aha, in such case the system build should use some specific -march anyway and
not just to disable `nopl'.

Andreas Schwab has reopened now this one, it should be NOTABUG:
http://sourceware.org/bugzilla/show_bug.cgi?id=6957


> > The flag `+nop' (such as `-march=i686+nop') does not work for me as expected
> > with HEAD and neither works with the patched code.
> 
> Please file a bug report.

I see your fix, thanks.


Thanks,
Jan

  reply	other threads:[~2011-02-08 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 17:11 Jan Kratochvil
2011-02-08 17:23 ` H.J. Lu
2011-02-08 19:01   ` Jan Kratochvil [this message]
2011-02-08 19:10     ` H.J. Lu
2011-02-08 20:00     ` Jakub Jelinek
2011-02-08 20:23       ` H.J. Lu
2011-02-09  6:43       ` Eirik Byrkjeflot Anonsen
2011-02-09 23:45         ` Quentin Neill
2011-02-10  6:51           ` Eirik Byrkjeflot Anonsen
2011-02-08 18:20 ` H.J. Lu

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=20110208190117.GA12119@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=aschwab@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=quentin.neill.gnu@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).