Re: [gentoo-user] Re: Firefox and clang

[Michael <confabulate@kintzios.com>]

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

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!  :-)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]