From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8057C138495 for ; Mon, 14 Jan 2013 21:53:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7BEB021C08C; Mon, 14 Jan 2013 21:53:33 +0000 (UTC) Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E0B6021C066 for ; Mon, 14 Jan 2013 21:53:31 +0000 (UTC) Received: by mail-ob0-f179.google.com with SMTP id x4so4352141obh.24 for ; Mon, 14 Jan 2013 13:53:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8lUjjO3t2a6NG+7U2EuJXAN5easakG6iZI26laJA7wg=; b=gxkBUR2EuLJcOJ3GmtIb6xPDCowVHjp9vVR8VpNqULTPNqzpyXO0E0juOWrWE0ozxB royEwDgrMOcDv+UgvOlKZRh9g3SQlJzrXRZkbf3LVza8EjEO6gjeeu4ZyRsmlc9m2b/q yFi4J0McHmciUFdh+gVGIg0jCYAyM8ZsGdgM6FXm4R3sKZRFARWNq/idrEwMbBXpyyck jj20MtVdLc9GhxvtgVGabmaKWbvza1wxkYXVZL9Vr945XZ9yocHBDvciE+8DiLWO/ZRw PSoCwYhSYnCiSJug6N0HbVIdhkZTX4kBSKsWCNCySbUNbfH51vkFIIPaDjtrc7ydF1jJ 7Suw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.60.169.205 with SMTP id ag13mr53638011oec.40.1358200411030; Mon, 14 Jan 2013 13:53:31 -0800 (PST) Received: by 10.60.20.234 with HTTP; Mon, 14 Jan 2013 13:53:30 -0800 (PST) In-Reply-To: References: Date: Tue, 15 Jan 2013 08:53:30 +1100 Message-ID: Subject: Re: [gentoo-user] How reliable is emerge --info output? From: Adam Carter To: "gentoo-user@lists.gentoo.org" Content-Type: multipart/alternative; boundary=bcaec5523a6408866104d346ad52 X-Archives-Salt: 1c0d1981-2abc-4c5e-9167-05464f86f9fa X-Archives-Hash: 436a558c61bb25a1dc571b26a5f6158f --bcaec5523a6408866104d346ad52 Content-Type: text/plain; charset=ISO-8859-1 > # 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 --bcaec5523a6408866104d346ad52 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

=
=A0 # Set optimization level
=A0 =A0 =A0 =A0 if [[ ${ARCH} =3D=3D hppa ]]; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "more than -O0 caus= es a segfault on
hppa" --enable-optimize=3D-O0
=A0 =A0 =A0 =A0 elif [[ ${ARCH} =3D=3D x86 ]]; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "less then -O2 caus= es a segfault on
x86" --enable-optimize=3D-O2
=A0 =A0 =A0 =A0 elif use custom-optimization || [[ ${ARCH} =3D~ (alpha|ia64= ) ]]; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Set optimization level based on CFLAGS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if is-flag -O0; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "fr= om CFLAGS" --enable-optimize=3D-O0
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elif [[ ${ARCH} =3D=3D ppc ]] && ha= s_version
'>=3Dsys-libs/glibc-2.8'; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "mo= re than -O1 segfaults on
ppc with glibc-2.8" --enable-optimize=3D-O1
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elif is-flag -O3; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "fr= om CFLAGS" --enable-optimize=3D-O3
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elif is-flag -O1; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "fr= om CFLAGS" --enable-optimize=3D-O1
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elif is-flag -Os; then
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "fr= om CFLAGS" --enable-optimize=3D-Os
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 else
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "Ge= ntoo's default
optimization" --enable-optimize=3D-O2
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 fi
=A0 =A0 =A0 =A0 else
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # Enable Mozilla's default
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mozconfig_annotate "mozilla default&qu= ot; --enable-optimize
=A0 =A0 =A0 =A0 fi
"""

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

=A0=A0=A0=A0=A0=A0=A0 # Strip optimization so it does not end up in com= pile string
=A0=A0=A0=A0=A0=A0=A0 filter-flags '-O*'

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