From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Firefox and clang
Date: Fri, 01 Nov 2024 14:08:00 -0400 [thread overview]
Message-ID: <7E22S2ZK.VUVCKMTV.D3T27CBF@IVOECD6Q.ZOTFYESC.7DTQ4WP4> (raw)
In-Reply-To: <5036054.0VBMTVartN@rogueboard>
I sent my previous reply before seeing this, and I have still not
received Marco's message, which explains thing better then I did.
On 2024.11.01 13:50, Michael wrote:
> On Friday 1 November 2024 17:00:20 GMT Marco Rebhan wrote:
> > On Friday, 1 November 2024 17:41:25 CET Michael wrote:
> > > Without USE="clang" the emerge takes 12-18% longer, but I am not
> sure what
> > > is the recommended compiler for FF or why it was changed.
> >
> > Hi Michael,
> >
> > https://bugs.gentoo.org/941878 seems to be the relevant bug with
> discussion
> > on why it was changed.
>
> Thanks! From what I read briefly, I understand clang is recommended
> upstream
> and therefore was set as a default flag. However, a rust Vs rust-bin
> version
> clash can occur and since FF patched their code to work with gcc,
> setting
> clang as the default compiler is no longer considered necessary - at
> least
> this is the present status.
>
> I don't know what the runtime performance impact may be of the
> current clang
> Vs gcc[1], but compilation times were longer on my systems, loosely
> comparing
> FF versions 128.3.1 to 128.4.0.
>
> [1]
> https://stackoverflow.com/questions/3187414/clang-vs-gcc-which-produces-faster-binaries
>
>
> > > PS. Also I do not understand the meaning of these notations:
> > >
> > > IUSE="foo"
> >
> > Everything outside the quotes is normal bash syntax, the variable
> contents
> > are interpreted by Portage.
> >
> > This sets the ebuild to have USE flags "foo". (If IUSE was set
> before this
> > line, it will clear out all the USE flags that were defined before.)
> >
> > > IUSE="+foo"
> >
> > This sets the ebuild to have USE flags "foo", the preceding "+" on
> the USE
> > flag means it is enabled by default.
> >
> > > IUSE+="foo"
> >
> > This appends to the previous IUSE value. Equivalent to
> IUSE="${IUSE}foo"
> > (note the missing space, hence why the Firefox ebuild uses IUSE+="
> foo"
> > instead).
> >
> > Cheers,
> > Marco
>
> Thanks for this clear and succinct explanation! :-)
>
next prev parent reply other threads:[~2024-11-01 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 11:15 [gentoo-user] Firefox and clang Michael
2024-11-01 14:43 ` [gentoo-user] " Jack Ostroff
2024-11-01 16:41 ` Michael
2024-11-01 17:00 ` Marco Rebhan
2024-11-01 17:50 ` Michael
2024-11-01 18:08 ` Jack [this message]
2024-11-04 7:27 ` Wols Lists
2024-11-04 15:12 ` Philip Webb
2024-11-01 18:05 ` Jack
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=7E22S2ZK.VUVCKMTV.D3T27CBF@IVOECD6Q.ZOTFYESC.7DTQ4WP4 \
--to=ostroffjh@users.sourceforge.net \
--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