public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "themgt at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/26176] -mtune=i686 builds code including CMOV
Date: Wed, 08 Feb 2006 17:30:00 -0000	[thread overview]
Message-ID: <20060208172957.20897.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26176-12158@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from themgt at mail dot ru  2006-02-08 17:29 -------
i586-pc-linux-gnu-gcc -c -Os -march=i586 -mtune=i686 -pipe -fomit-frame-pointer
-fno-strict-aliasing  -ansi -Wno-return-type -w    -I../..
-I../../exports/include   -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L         
                   -D_POSIX_SOURCE -D_XOPEN_SOURCE               -D_BSD_SOURCE
-D_SVID_SOURCE                                 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64                                  -D_GNU_SOURCE          
                 -DFUNCPROTO=15 -DNARROWPROTO   -DHASXDMAUTH   Wraphelp.c

What do you want to see? Something like this?
This is part of the output while emerging/compiling xorg.

"-Os -march=i586 -mtune=i686 -pipe -fomit-frame-pointer" is part of any compile
process, i can see that without the -v flag


-- 


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


  parent reply	other threads:[~2006-02-08 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 16:10 [Bug other/26176] New: " themgt at mail dot ru
2006-02-08 16:16 ` [Bug other/26176] " rguenth at gcc dot gnu dot org
2006-02-08 17:00 ` [Bug target/26176] " pinskia at gcc dot gnu dot org
2006-02-08 17:30 ` themgt at mail dot ru [this message]
2006-02-09 10:06 ` rguenth at gcc dot gnu dot org
2006-02-09 21:08 ` themgt at mail dot ru

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=20060208172957.20897.qmail@sourceware.org \
    --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).