| 2023-04-12 20:44:20 |
Mark Esler |
bug |
|
|
added bug |
| 2023-07-24 08:27:16 |
Matthias Klose |
bug task added |
|
dpkg (Ubuntu) |
|
| 2023-07-25 17:18:36 |
Matthias Klose |
gcc-12 (Ubuntu): status |
New |
Invalid |
|
| 2023-07-25 19:19:18 |
Mark Esler |
gcc-12 (Ubuntu): status |
Invalid |
New |
|
| 2023-07-25 23:09:18 |
Mark Esler |
dpkg (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2023-07-25 23:09:21 |
Mark Esler |
gcc-12 (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2023-07-26 05:40:11 |
Matthias Klose |
gcc-12 (Ubuntu): status |
New |
Won't Fix |
|
| 2023-07-26 14:53:45 |
Mark Esler |
gcc-12 (Ubuntu): status |
Won't Fix |
New |
|
| 2023-07-26 19:09:22 |
Mark Esler |
tags |
|
sec-1935 |
|
| 2023-10-18 17:57:29 |
Jay Vosburgh |
bug |
|
|
added subscriber Jay Vosburgh |
| 2023-10-30 22:16:27 |
Mark Esler |
description |
This flag has a long history of distro use in Fedora [0] and is used
by Gentoo [1].
_GLIBCXX_ASSERTIONS was developed not to impact ABI or big-O complexity.
> 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.
[2]
As with -D_FORTIFY_SOURCE=3, poor quality code requires more mitigations
and therefore have higher performance penalties.
When Fedora initially added this default flag some packages FTBFS. Now
packages appear stable.
[0] https://src.fedoraproject.org/rpms/redhat-rpm-config/c/0d162176e9dba1adc330a9ee561b91c8e5e62cb5
[1] https://bugs.gentoo.org/876895
[2] https://bugs.launchpad.net/kicad/+bug/1838448/comments/40 |
> 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. [1]
_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://bugs.launchpad.net/kicad/+bug/1838448/comments/40
[1] https://github.com/jvoisin/compiler-flags-distro |
|
| 2023-10-30 22:17:14 |
Mark Esler |
bug task added |
|
gcc-13 (Ubuntu) |
|
| 2023-10-30 22:17:27 |
Mark Esler |
gcc-13 (Ubuntu): importance |
Undecided |
High |
|
| 2023-10-30 22:17:31 |
Mark Esler |
gcc-13 (Ubuntu): milestone |
|
ubuntu-24.04 |
|
| 2023-10-30 22:27:09 |
Mark Esler |
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. [1]
_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://bugs.launchpad.net/kicad/+bug/1838448/comments/40
[1] https://github.com/jvoisin/compiler-flags-distro |
> 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://bugs.launchpad.net/kicad/+bug/1838448/comments/40
[1] https://github.com/jvoisin/compiler-flags-distro |
|
| 2023-10-30 22:42:44 |
Mark Esler |
bug |
|
|
added subscriber Ubuntu Security Team |
| 2023-12-13 23:05:06 |
Mark Esler |
gcc-13 (Ubuntu): milestone |
ubuntu-24.04 |
|
|
| 2023-12-13 23:05:44 |
Mark Esler |
gcc-13 (Ubuntu): importance |
High |
Medium |
|
