Сравнение libstdc++-v3-3.3.6-r4 с libstdc++-v3-3.3.6-r5
| /usr/portage/sys-libs/libstdc++-v3/libstdc++-v3-3.3.6-r5.ebuild 2026-01-24 11:18:05.051003610 +0300 | ||
|---|---|---|
| 1 |
# Copyright 1999-2025 Gentoo Authors |
|
| 1 |
# Copyright 1999-2026 Gentoo Authors |
|
| 2 | 2 |
# Distributed under the terms of the GNU General Public License v2 |
| 3 | 3 | |
| 4 | 4 |
EAPI=8 |
| ... | ... | |
| 74 | 74 |
do_filter_flags() {
|
| 75 | 75 |
declare setting newflags |
| 76 | 76 | |
| 77 |
# In general gcc does not like optimization, and add -O2 where |
|
| 77 |
# In general gcc does not like optimization, and add -O1 where |
|
| 78 | 78 |
# it is safe. This is especially true for gcc 3.3 + 3.4 |
| 79 |
# Compiler crash with -O2, bug #940229 |
|
| 79 | 80 |
if is-flagq -O?; then |
| 80 |
newflags+=" -O2" |
|
| 81 |
newflags+=" -O1" |
|
| 81 | 82 |
fi |
| 82 | 83 | |
| 83 | 84 |
# gcc 3.3 doesn't support -mtune on numerous archs, so xgcc will fail |
| ... | ... | |
| 105 | 106 |
# 3.3 supports disabling this optimization. |
| 106 | 107 |
newflags+=" -fno-strict-aliasing" |
| 107 | 108 | |
| 109 |
# Force older c standard due to incompatibilities, bug #944234 |
|
| 110 |
newflags+=" -std=gnu99" |
|
| 111 | ||
| 108 | 112 |
# xgcc wont understand gcc 3.4 flags... in fact it won't understand most |
| 109 | 113 |
# things or have most patches, regardless of what the real GCC understands. |
| 110 | 114 |
# A random collection of bugs: |