[SERVER-61081] Disable stringop-truncation and array-bounds warnings when building with GCC 11 Created: 28/Oct/21 Updated: 27/Oct/23 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||
| Sprint: | Dev Platform 2021-11-15, Dev Platform 2021-11-29, Dev Platform 2022-03-21 | ||||||||
| Participants: | |||||||||
| Description |
|
We've had a few instances when using the toolchain v4 GCC 11 where small code changes have either caused the emergence of novel instances of these types of warnings, or where spooky local modifications have caused existing instances to disappear. Changing optimization levels also moves around where they seem to pop up. It isn't reasonable to expect developers to chase these down as they appear in the waterfall builders using GCC 11. For now, suppress these warnings globally when using GCC 11, and we will file a compensating ticket to pursue reenabling them. |