[CI/CD/CDASH] Disable L1 cxx optimization for Profiling builds if gcc 10.2.1

• Add flag (cmake option) to disable the L1 optimization
• Auto-set this flag if a Profiling build with gcc 10.2.1 is detected

=> Compiler crashes indicate things to fix on compiler side, NOT on our side! => But at least with this we avoid the crash

See Redmine Refs #2590

requested review from @f.uhlig

Dear @se.gorbunov, @s.zharko,

you have been identified as code owner of at least one file which was changed with this merge request.

Please check the changes and approve them or request changes.

added CodeOwners label

added 1 commit

• 83c31d02 - [CI/CD/CDASH] Disable L1 cxx optimization for Profiling builds if gcc 10.2.1

Compare with previous version

marked this merge request as ready

changed title from Draft: DO NOT MERGE! remove L1 specific cxx opti flag to prevent pb with Weekly build and gcc10.2 to [CI/CD/CDASH] Disable L1 cxx optimization for Profiling builds if gcc 10.2.1

added BugFix CI/CD labels

assigned to @f.uhlig

changed the description

added 1 commit

• b038ce02 - [CI/CD/CDASH] Disable L1 cxx optimization for Profiling builds if gcc 10.2.1

Compare with previous version

added 1 commit

• 6230c165 - [CI/CD/CDASH] Disable L1 cxx optimization for Profiling builds if gcc 10.2.1

Compare with previous version

approved this merge request

added 4 commits

• 6230c165...34993f60 - 3 commits from branch computing:master
• 39253604 - [CI/CD/CDASH] Disable L1 cxx optimization for Profiling builds if gcc 10.2.1

Compare with previous version

enabled an automatic merge when the pipeline for 39253604 succeeds

merged

@f.uhlig Do you think this should be backported to the release candidate?
I just stumbled on it while trying to generate full CDASH tests (using the Weeklies) of the release for the three valid combinations of vaeXX vs FS + FR for future reference, e.g. when doing the next release:

• baselines of runtime per test
• logs amounts
• warnings
• failing tests