Update gcc CI to use gcc-11 container#59202
Conversation
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
e135661 to
3de8738
Compare
eng/native/configurecompiler.cmake
Outdated
There was a problem hiding this comment.
This condition was missed out previously, and was failing the libs.native subset build with gcc (which we currently don't exercise in the CI and maybe we can; since it takes 30-60 seconds max)
3de8738 to
21756e6
Compare
|
gcc leg has picked up the newer version: no compiler warnings. There is one preexisting assembler warning which remained, however: I haven't looked too deep but I think it is not related to GSCookie, or it is benign. The compiled binaries do have all the exported symbols in correct segments which we typically find when compiled with clang (like the ones which SOS looks for). |
With gcc9 leg, we had 2500+ warnings in JIT due to a bit field width issue: #33541.
Now that we have a dedicated gcc container, it is easier to upgrade gcc toolchain independent from llvm toolchain.
This PR uses the latest gcc 11 prereq image. The bitfield width warnings have been fixed in this version, therefore I have enabled Werror in the JIT for gcc version >= 11.
Fixes #33541