[gentoo-user] chromium-65.0.3325.146 compilation warnings

[gentoo-user] chromium-65.0.3325.146 compilation warnings

[Mick]

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

I can see a few warnings pilling up on different systems when trying to emerge 
chromium-65.0.3325.146:

warning: unknown warning option '-Wno-enum-compare-switch'; did you mean '-
Wno-enum-compare'? [-Wunknown-warning-option]
warning: unknown warning option '-Wno-tautological-unsigned-zero-compare' [-
Wunknown-warning-option]
warning: unknown warning option '-Wno-null-pointer-arithmetic'; did you mean 
'-Wno-null-arithmetic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wno-tautological-constant-compare'; did you 
mean '-Wno-tautological-pointer-compare'? [-Wunknown-warning-option]
4 warnings generated.

Does this mean I should be using a different gcc or CFLAGS?

They mostly are:

CFLAGS="-march=native -O2 -pipe"

-- 
Regards,
Mick

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

Re: [gentoo-user] chromium-65.0.3325.146 compilation warnings

[Alexander Kapshuk]

On Mon, Mar 12, 2018 at 10:17 AM, Mick <michaelkintzios@gmail.com> wrote:
> I can see a few warnings pilling up on different systems when trying to emerge
> chromium-65.0.3325.146:
>
> warning: unknown warning option '-Wno-enum-compare-switch'; did you mean '-
> Wno-enum-compare'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-unsigned-zero-compare' [-
> Wunknown-warning-option]
> warning: unknown warning option '-Wno-null-pointer-arithmetic'; did you mean
> '-Wno-null-arithmetic'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-constant-compare'; did you
> mean '-Wno-tautological-pointer-compare'? [-Wunknown-warning-option]
> 4 warnings generated.
>
> Does this mean I should be using a different gcc or CFLAGS?
>
> They mostly are:
>
> CFLAGS="-march=native -O2 -pipe"
>
> --
> Regards,
> Mick

On my x86 system, I've been seeing similar warnings being generated by
clang when compiling the ffmpeg that comes with chromium.
I've also hit another bug related to that, where clang compilation
terminates with an error message along the lines of there being not
enough registers available.
There's a bug registered for that in chromium bugzilla, which I can't
reference at the moment. So far, no solution has been implemented, as
far as I could tell.

Re: [gentoo-user] chromium-65.0.3325.146 compilation warnings

[Mick]

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

On Monday, 12 March 2018 08:27:31 GMT Alexander Kapshuk wrote:
> On Mon, Mar 12, 2018 at 10:17 AM, Mick <michaelkintzios@gmail.com> wrote:
> > I can see a few warnings pilling up on different systems when trying to
> > emerge chromium-65.0.3325.146:
> > 
> > warning: unknown warning option '-Wno-enum-compare-switch'; did you mean
> > '-
> > Wno-enum-compare'? [-Wunknown-warning-option]
> > warning: unknown warning option '-Wno-tautological-unsigned-zero-compare'
> > [- Wunknown-warning-option]
> > warning: unknown warning option '-Wno-null-pointer-arithmetic'; did you
> > mean '-Wno-null-arithmetic'? [-Wunknown-warning-option]
> > warning: unknown warning option '-Wno-tautological-constant-compare'; did
> > you mean '-Wno-tautological-pointer-compare'? [-Wunknown-warning-option]
> > 4 warnings generated.
> > 
> > Does this mean I should be using a different gcc or CFLAGS?
> > 
> > They mostly are:
> > 
> > CFLAGS="-march=native -O2 -pipe"
> > 
> > --
> > Regards,
> > Mick
> 
> On my x86 system, I've been seeing similar warnings being generated by
> clang when compiling the ffmpeg that comes with chromium.
> I've also hit another bug related to that, where clang compilation
> terminates with an error message along the lines of there being not
> enough registers available.
> There's a bug registered for that in chromium bugzilla, which I can't
> reference at the moment. So far, no solution has been implemented, as
> far as I could tell.

Right, clang's the culprit ... thanks for letting me know.  An amd64 system 
completed the emerge without problems, two others are still chugging along.
-- 
Regards,
Mick

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

[gentoo-user] Re: chromium-65.0.3325.146 compilation warnings

[Nikos Chantziaras]

On 12/03/18 10:17, Mick wrote:
> I can see a few warnings pilling up on different systems when trying to emerge
> chromium-65.0.3325.146:
> 
> warning: unknown warning option '-Wno-enum-compare-switch'; did you mean '-
> Wno-enum-compare'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-unsigned-zero-compare' [-
> Wunknown-warning-option]
> warning: unknown warning option '-Wno-null-pointer-arithmetic'; did you mean
> '-Wno-null-arithmetic'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-constant-compare'; did you
> mean '-Wno-tautological-pointer-compare'? [-Wunknown-warning-option]
> 4 warnings generated.
> 
> Does this mean I should be using a different gcc or CFLAGS?

No. What these warnings mean is that the chromium build system is
passing these options to the compiler:

   -Wno-enum-compare-switch -Wno-tautological-unsigned-zero-compare
   -Wno-null-pointer-arithmetic -Wno-tautological-constant-compare

but the compiler version installed on your system doesn't support them.

Your own CFLAGS got nothing to do with this. Furthermore, these warnings 
are of no interest to you whatsoever, unless you're a chromium developer.

GCC 7.3 and Clang 6.0 do support these options, but if you're using a 
version that doesn't, it's of no consequence. Warning options do not 
affect code generation.

Re: [gentoo-user] Re: chromium-65.0.3325.146 compilation warnings

[Mick]

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

On Monday, 12 March 2018 17:11:16 GMT Nikos Chantziaras wrote:

> No. What these warnings mean is that the chromium build system is
> passing these options to the compiler:
> 
>    -Wno-enum-compare-switch -Wno-tautological-unsigned-zero-compare
>    -Wno-null-pointer-arithmetic -Wno-tautological-constant-compare
> 
> but the compiler version installed on your system doesn't support them.
> 
> Your own CFLAGS got nothing to do with this. Furthermore, these warnings
> are of no interest to you whatsoever, unless you're a chromium developer.

I don't believe I possess the abilities to be developer.  :-)


> GCC 7.3 and Clang 6.0 do support these options, but if you're using a
> version that doesn't, it's of no consequence. Warning options do not
> affect code generation.

OK, I think it's clang what done it.  I'm on gcc-7.3.0, but clang-5.0.1.

-- 
Regards,
Mick

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