Please add -D_GLIBCXX_ASSERTIONS to default build flags
Bug #2016042 reported by
Mark Esler
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
New
|
Wishlist
|
Unassigned | ||
gcc-12 (Ubuntu) |
New
|
Wishlist
|
Unassigned | ||
gcc-13 (Ubuntu) |
New
|
Medium
|
Unassigned | ||
gcc-14 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
> The _GLIBCXX_ASSERTIONS macro defines a subset of the _GLIBCXX_DEBUG
> checks, with no impact on class layout and minimal impact on runtime
> (and no changes in algorithmic complexity). It is intended to be
> suitable for both debug builds and release builds. [0]
_GLIBCXX_ASSERTIONS was developed not to impact ABI or big-O complexity.
Distros which use this flag include Fedora (2018), Arch Linux (2021) Gentoo Hardened (2022), Alpine (2023), and OpenSUSE [1].
[0] https:/
[1] https:/
Changed in dpkg (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in gcc-12 (Ubuntu): | |
importance: | Undecided → Wishlist |
tags: | added: sec-1935 |
description: | updated |
Changed in gcc-13 (Ubuntu): | |
importance: | Undecided → High |
milestone: | none → ubuntu-24.04 |
description: | updated |
To post a comment you must log in.
this is added to Fedora's and Gentoo's build systems. No, this definitely not a GCC default setting