public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/39851]  New: gcc -Q --help=target does not list extensions selected by -march=
Date: Wed, 22 Apr 2009 14:58:00 -0000	[thread overview]
Message-ID: <bug-39851-15322@http.gcc.gnu.org/bugzilla/> (raw)

Even though -march=nocona enables SSE2 and SSE3 extensions, gcc -Q
--help=target does not list them as enabled.  This may be confusing to the user
(see http://gcc.gnu.org/ml/gcc-help/2009-04/msg00293.html ):

$ gcc -Q --help=target -march=nocona | grep msse[23]
  -msse2                                [disabled]
  -msse3                                [disabled]

-msse[23] would be enabled in gcc/config/i386/i386.c:override_options(), called
from toplev.c:process_options(), which is in turn called from do_compile(). 
OTOH, --help=target is processed in decode_options(), which is executed before
do_compile.  It would be nice if --help=target processing could see options
overridden by target backend.


-- 
           Summary: gcc -Q --help=target does not list extensions selected
                    by -march=
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: driver
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: amonakov at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39851


             reply	other threads:[~2009-04-22 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 14:58 amonakov at gcc dot gnu dot org [this message]
2009-04-22 23:29 ` [Bug other/39851] " pinskia at gcc dot gnu dot org

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=bug-39851-15322@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).