public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] How reliable is emerge --info output?
Date: Tue, 15 Jan 2013 08:53:30 +1100	[thread overview]
Message-ID: <CAC=wYCHOnLJA9k8P4QWVL5JDbHxvmoz-3-rWS6Bim54FH02B2w@mail.gmail.com> (raw)
In-Reply-To: <CAG2nJkO70K+y3jAUkDHzwQwqG5rOhoVVp9qCpBi1fNdhwgFMzg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

>   # Set optimization level
>         if [[ ${ARCH} == hppa ]]; then
>                 mozconfig_annotate "more than -O0 causes a segfault on
> hppa" --enable-optimize=-O0
>         elif [[ ${ARCH} == x86 ]]; then
>                 mozconfig_annotate "less then -O2 causes a segfault on
> x86" --enable-optimize=-O2
>         elif use custom-optimization || [[ ${ARCH} =~ (alpha|ia64) ]]; then
>                 # Set optimization level based on CFLAGS
>                 if is-flag -O0; then
>                         mozconfig_annotate "from CFLAGS"
> --enable-optimize=-O0
>                 elif [[ ${ARCH} == ppc ]] && has_version
> '>=sys-libs/glibc-2.8'; then
>                         mozconfig_annotate "more than -O1 segfaults on
> ppc with glibc-2.8" --enable-optimize=-O1
>                 elif is-flag -O3; then
>                         mozconfig_annotate "from CFLAGS"
> --enable-optimize=-O3
>                 elif is-flag -O1; then
>                         mozconfig_annotate "from CFLAGS"
> --enable-optimize=-O1
>                 elif is-flag -Os; then
>                         mozconfig_annotate "from CFLAGS"
> --enable-optimize=-Os
>                 else
>                         mozconfig_annotate "Gentoo's default
> optimization" --enable-optimize=-O2
>                 fi
>         else
>                 # Enable Mozilla's default
>                 mozconfig_annotate "mozilla default" --enable-optimize
>         fi
> """
>

And just after that, it appears that if custom-cflags is not set, then it
strips all the -O* flags (if i'm reading the code correctly), which would
explain why there's no -O set for the compiler.....

        # Strip optimization so it does not end up in compile string
        filter-flags '-O*'

        # Strip over-aggressive CFLAGS
        use custom-cflags || strip-flags

[-- Attachment #2: Type: text/html, Size: 2322 bytes --]

      reply	other threads:[~2013-01-14 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 11:18 [gentoo-user] How reliable is emerge --info output? Adam Carter
2013-01-14 11:45 ` Bruce Hill
2013-01-14 12:05 ` Mark David Dumlao
2013-01-14 21:53   ` Adam Carter [this message]

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='CAC=wYCHOnLJA9k8P4QWVL5JDbHxvmoz-3-rWS6Bim54FH02B2w@mail.gmail.com' \
    --to=adamcarter3@gmail.com \
    --cc=gentoo-user@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