From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: GCC-4.5.2 Has Serious Problems
Date: Fri, 1 Jul 2011 01:22:46 -0400 [thread overview]
Message-ID: <20110701012246.276ce8e6.frank.peters@comcast.net> (raw)
In-Reply-To: <BANLkTi=EGgO7mewhFRpxqF2usULcevo0JQ@mail.gmail.com>
On Thu, 30 Jun 2011 21:36:38 -0700
Mark Knecht <markknecht@gmail.com> wrote:
>
> I think it's completely appropriate for this list. This distro expects
> that we put CFLAG options in make.conf so I need to hear about this
> stuff even if I don't have to background to completely understand
> what's really causing the problem.
>
In this case, or in the case of any program where "-fno-strict-aliasing"
could make a difference, the maintainer of the program would include
the option in the ebuild. The user would not have to worry too much
about it.
But yes, it is always good to know about the compiler flags.
To see exactly what compile flags are being used in your programs, here
is a neat method I picked up from somewhere. Just open a terminal and
enter the following command:
echo 'int main(){return 0;}' > test.c && gcc -v -Q $CFLAGS test.c -o test && rm test.c test
In place of $CFLAGS just substitute any option of interest. There will
be a flood of output, but just scroll back a few lines to find the "options
passed:" and "options enabled:" sections.
For example, using "-O2" for $CFLAGS indicates that "-fstrict-aliasing" is
used, but it is not used with "-O1."
It also shows that with "-O2" the option "-mno-sse4" is used, and so if
you want to use SSE4 for certain programs (e.g. video, audio) you will
need to specifically enable it.
There may be an even slicker way to reveal the flags, but this is the
only way I know.
Frank Peters
next prev parent reply other threads:[~2011-07-01 5:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:45 [gentoo-amd64] GCC-4.5.2 Has Serious Problems Frank Peters
2011-06-30 22:30 ` Alex Schuster
2011-06-30 23:34 ` Frank Peters
2011-06-30 23:35 ` [gentoo-amd64] " Nikos Chantziaras
2011-06-30 23:44 ` Nikos Chantziaras
2011-07-01 0:04 ` Frank Peters
2011-07-01 0:11 ` Nikos Chantziaras
2011-07-01 0:58 ` Duncan
2011-07-01 1:23 ` Frank Peters
2011-07-01 1:52 ` Duncan
2011-07-01 2:15 ` Ian McCulloch
2011-07-01 4:36 ` Mark Knecht
2011-07-01 5:22 ` Frank Peters [this message]
2011-07-01 0:25 ` Frank Peters
2011-07-01 1:04 ` Frank Peters
2011-07-01 2:18 ` Duncan
2011-07-01 2:22 ` Barry Schwartz
2011-07-01 2:43 ` Frank Peters
2011-07-01 11:53 ` Nikos Chantziaras
2011-07-01 16:53 ` Frank Peters
-- strict thread matches above, loose matches on Subject: below --
2011-07-01 2:30 Ian McCulloch
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=20110701012246.276ce8e6.frank.peters@comcast.net \
--to=frank.peters@comcast.net \
--cc=gentoo-amd64@lists.gentoo.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