1611519 - (build-gcc-10) [meta] Build with gcc 10

Status: RESOLVED FIXED

(Developer Infrastructure :: Source Code Analysis, task)

Description

[Sylvestre Ledru [:Sylvestre]]

Just like we did with gcc 8 & 9

Comment 1

[František Zatloukal]

https://bugzilla.mozilla.org/show_bug.cgi?id=1612797 might be added here as "depends on"?

Comment 2

[Axel Viala]

Hi Sylvestre, I suggest you to add -fanalyzer option somewhere in the build with gcc10 if not already done, found some CWE in C/C++ projects with this fabulous warning, might be a good one to share with Mozilla teams using C/C++ and security reviewer of 3rd party codes.

Detailed article: https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10/

Comment 3

[ISHIKAWA, Chiaki]

Hi,
Is this bugzilla meant to collect GCC-10 relaed issues?

If so, here is one.
I build C-C thunderbird locally to test my patches and use GCC compiler mainly because that is my compiler for choice for various reasons (having done embedded programming using GCC).
Occasionally, new versions of GCC exhibit issues such as internal compiler error and I see one with GCC-10 right now.
I reported it as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98000.
There does not seem to be any workaround yet.

Comment 4

[Sylvestre Ledru [:Sylvestre]]

Is this bugzilla meant to collect GCC-10 relaed issues?

Yes but please open separate bugs :)

Comment 5

[ISHIKAWA, Chiaki]

(In reply to Sylvestre Ledru [:Sylvestre] from comment #4)

Is this bugzilla meant to collect GCC-10 relaed issues?

Yes but please open separate bugs :)

Will do. Actually, it looks there are more bugs related to the root cause of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98000. I will file them anyway in the next couple of days.

Comment 6

[ISHIKAWA, Chiaki]

(In reply to Axel Viala from comment #2)

Hi Sylvestre, I suggest you to add -fanalyzer option somewhere in the build with gcc10 if not already done, found some CWE in C/C++ projects with this fabulous warning, might be a good one to share with Mozilla teams using C/C++ and security reviewer of 3rd party codes.

Detailed article: https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10/

This check probably should be done maybe once a day for all the platforms where this -fanalyze is supported.
Once a day, because this compilation with -fanalyze is memory hog. I have 16GB assigned to my VirtualBox image running under Windows10 on my home PC. During the compilation of C-C TB with -analyze , I saw swap growing to 8GB (with much paging activity) and sure enough there are many CWEs in the code to my surprise in M-C and C-C trees, but memory pressure is something people need to be aware of. It is not something you may want to run too often.