https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115208
--- Comment #7 from Sergei Trofimovich ---
(In reply to Andrew Macleod from comment #6)
> Created attachment 58287 [details]
> proposed patch
>
> I'm testing this patch, does it resolve your problem?
>
> I forgot to free the gori_nmap object
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #24 from Sergei Trofimovich ---
Thank you, Alexander! Tricky `REG_EQUAL` makes sense.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115227
Bug ID: 115227
Summary: [15 Regression] i686-linux fails frequently with cc1:
out of memory allocating x bytes after a total of ~4GB
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #22 from Sergei Trofimovich ---
(In reply to Sergei Trofimovich from comment #21)
gcc generates the following code for this C code:
> int main() {
> const __m128i su = _mm_set1_epi32(0x4f80);
> const __m128 sf =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #21 from Sergei Trofimovich ---
Shrunk the example down to a single simpler function while preserving the
original masking intent:
```c
cat bug.cc
#include
#include
#include
__attribute__((noipa))
static void assert_eq_p(void *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #15 from Sergei Trofimovich ---
> I shrunk bug.cc slightly further into shorter-bug.cc and now it fails
> equally on gcc-13 and gcc-15. I agree that gcc-15 just got more constant
> folds available now, but otherwise it's behaviour
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #14 from Sergei Trofimovich ---
Created attachment 58265
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58265=edit
shorter-bug.cc
I shrunk bug.cc slightly further into shorter-bug.cc and now it fails equally
on gcc-13 and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #8 from Sergei Trofimovich ---
Thank you, Jakub!
> The reason the testcase FAILs is the same as in the other PRs, it is trying
> to convert {0x0.8p+33f, 0x0.8p+33f, 0x0.8p+33f, 0x0.8p+33f} V4SFmode vector
> to V4SImode, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #3 from Sergei Trofimovich ---
Looking at -O2's bug.cc.265t.optimized tree optimizations come up with unfolded
saturated sub8:
_12 = __builtin_ia32_psubusb128 ({ -65, 0, 0, 0, -65, 0, 0, 0, -65, 0, 0, 0,
-65, 0, 0, 0 }, { -99, 0,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115115
--- Comment #11 from Sergei Trofimovich ---
After `highway` applied a masking fix to `highway/master` `gcc-15` still fails
to pass the `HwyConvertTestGroup/HwyConvertTest.TestAllF2IPromoteTo/SSE2`.
I tried to reduce the test with more care and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
Sergei Trofimovich changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
Bug ID: 115161
Summary: [15 Regression] highway-1.0.7 miscompilation of some
SSE2 intrinsics
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115146
--- Comment #9 from Sergei Trofimovich ---
(In reply to Levy Hsu from comment #7)
> Created attachment 58236 [details]
> [PR]115146
The change fixed `highway-1.0.7` testsuite failure for me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115146
--- Comment #4 from Sergei Trofimovich ---
(In reply to Sergei Trofimovich from comment #3)
> Bisected down to r15-498-gc6cc6d4741a880
Sorry, should be r15-499-ga71f90c5a7ae29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115146
Sergei Trofimovich changed:
What|Removed |Added
CC||admin at levyhsu dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115146
Sergei Trofimovich changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115146
--- Comment #1 from Sergei Trofimovich ---
Specifically if I change original example to contain 16 bytes instead of 8:
--- bug.c.orig 2024-05-18 11:07:47.426351557 +0100
+++ bug.c 2024-05-18 11:08:02.135601287 +0100
@@ -15,2 +15,2 @@
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115146
Bug ID: 115146
Summary: [15 Regression] Incorrect 8-byte vectorization:
psllw/psraw confusion
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115115
--- Comment #7 from Sergei Trofimovich ---
Filed https://github.com/google/highway/issues/2183 on `highway` upstream side.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115115
--- Comment #5 from Sergei Trofimovich ---
(In reply to Andrew Pinski from comment #2)
> So from a point of view of float to int conversion, both are valid for out
> of range values.
Looking at CVTTPS2DQ instruction from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115115
--- Comment #3 from Sergei Trofimovich ---
I might also have overzealously extracted simplified example from
highway-1.0.7: `gcc-14` (or older) do not fail on unmodified highway-1.0.7
testsuite.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115115
--- Comment #1 from Sergei Trofimovich ---
If I understand the test correctly it uses 2^63 floating point value and
converts it to uint32_t (or int32_t?).
gcc's constant-fold saturates it to 2^63-1 while CPU keeps it at 2^63 (as if it
was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115115
Bug ID: 115115
Summary: [12/13/14/15 Regression] highway-1.0.7 wrong
_mm_cvttps_epi32() constant fold
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
--- Comment #25 from Sergei Trofimovich ---
(In reply to Richard Biener from comment #24)
> (In reply to Sergei Trofimovich from comment #23)
> [...]
> > Why did `gcc` generate unconditional NULL dereference here? I suspect it
> > somehow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
--- Comment #23 from Sergei Trofimovich ---
At SIGSEGV site the code is an unconditional NULL dereference due to
dereference of `xor %esi,%esi` result from `gdb`.
797 if (op != _Py_NULL) {
0x7f940c871563 <+2563>: cmpq
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
--- Comment #22 from Sergei Trofimovich ---
Trying again to catch more precise place for SIGABRT.
Beginning at the start of the possibly aborting function:
(gdb) break __pyx_pf_4sage_4libs_3gap_7element_19GapElement_Function_2__call__
(gdb)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
--- Comment #21 from Sergei Trofimovich ---
Good point! I wonder if I'm looking at the backtrace too late (or at the wrong
one). I'll retry again this evening and will extract more context.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
--- Comment #18 from Sergei Trofimovich ---
> 2) ideally show a gdb session with the important events, which setjmp was it
> (I see _setjmp and __sigsetjmp calls in the function), which exact function
> called from the function ended up
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
--- Comment #17 from Sergei Trofimovich ---
> 1) attach your *.s file and state which exact compiler you used (revision)
Generate code first:
https://slyfox.uni.cx/b/gcc/PR114872/d.tar.gz (4MB, does not fit on bugzilla's
1MB limit)
is the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
Sergei Trofimovich changed:
What|Removed |Added
CC||slyfox at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114933
--- Comment #9 from Sergei Trofimovich ---
The mcfgthread change fixed the full gcc build for me. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114933
Sergei Trofimovich changed:
What|Removed |Added
CC||lh_mouse at 126 dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114933
Bug ID: 114933
Summary: [15 Regression] mcfgthread-1.6.1 typecheck failure:
error: explicit specializations are not permitted here
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114439
--- Comment #6 from Sergei Trofimovich ---
The change also fixed full icu4c-73.2 build for me. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114439
Sergei Trofimovich changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114439
Bug ID: 114439
Summary: [14 Regression] icu4c-73.2 build failure: invalid
initializer for array member
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111527
--- Comment #5 from Sergei Trofimovich ---
(In reply to Deepthi H from comment #4)
> I have been investigating this issue further. Hence checking the source code
> and debugging the gcc sources. However, I wasn't able to find where the
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113141
Sergei Trofimovich changed:
What|Removed |Added
CC||slyfox at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113445
--- Comment #10 from Sergei Trofimovich ---
The patch fixes bootstrap for me as well. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113445
Bug ID: 113445
Summary: [14 Regression] bootstrap failure on f95-lang.cc:
‘-fcompare-debug’ failure
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113132
Sergei Trofimovich changed:
What|Removed |Added
CC||tamar.christina at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113132
Bug ID: 113132
Summary: [14 regression] --enable-checking=release build fails:
tree-vect-loop.cc:6221:34: error:
‘vec_stmts.vec::m_vec’ may
be used uninitialized
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112991
--- Comment #5 from Sergei Trofimovich ---
The change also fixes p7zip-17.05 build for me. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112991
Bug ID: 112991
Summary: [14 Regression] ICE during GIMPLE pass: ifcvt on
p7zip-17.05
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112869
--- Comment #3 from Sergei Trofimovich ---
I confirm the proposed change fixes build of libopenmpt-0.7.3 as well. Thank
you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112869
Bug ID: 112869
Summary: [14 regression] ICE at gimplify_expr, at
gimplify.cc:17531 on libopenmpt-0.7.3
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112711
--- Comment #9 from Sergei Trofimovich ---
The change also fixes llvm-16.0.6 testsuite for me. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112711
--- Comment #3 from Sergei Trofimovich ---
I confirm bisect landed on r14-5831-gaae723d360ca26 as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112711
Bug ID: 112711
Summary: [14 Regression] possibly wrong code in bswap32(int) on
llvm-16.0.6 test suite
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112613
--- Comment #3 from Sergei Trofimovich ---
> since the bad instruction is a compare, it does seem like it might be solved
> via https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112572#c18 too. compare
> elimination is going wrong.
Yeah, that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112572
--- Comment #19 from Sergei Trofimovich ---
I spent some time poking at the bug and was not able to reproduce it on my
toolchain.
I was able to get it to fail on gentoo's toolchain and arrived at problems in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112613
--- Comment #1 from Sergei Trofimovich ---
Created attachment 56635
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56635=edit
bug.cpp.xz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112613
Bug ID: 112613
Summary: gcc generates incorrect argument reads at prologue
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112601
Bug ID: 112601
Summary: ICE in cgraph_node::verify_node(): error: invalid
calls_comdat_local flag
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112567
--- Comment #5 from Sergei Trofimovich ---
The fix allowed me to build linux-6.6.1 successfully with current gcc-master.
Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112567
Bug ID: 112567
Summary: [14 regression] ICE in RTL pass: split2: Segmentation
fault
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95194
Sergei Trofimovich changed:
What|Removed |Added
CC||slyfox at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112467
--- Comment #2 from Sergei Trofimovich ---
Filed a feature request on `clang` side to consider implementing it:
https://github.com/llvm/llvm-project/issues/71858
Meanwhile would it be reasonable to enable the attribute only for `gcc`?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112467
Bug ID: 112467
Summary: [14 Regression] libstdc++ fails to build on clang:
bits/stl_bvector.h:189:23: error: '__assume__'
attribute cannot be applied to a statement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112379
Sergei Trofimovich changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112379
--- Comment #1 from Sergei Trofimovich ---
Proposed trivial fix by marking helper as `ATTRIBUTE_UNUSED`:
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635194.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112379
Bug ID: 112379
Summary: [14 Regression] bootstrap failure on
--enable-checking=release: gcc/gcc-urlifier.cc:100:1:
error: get_url_suffix_for_quoted_text() defined but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112347
--- Comment #8 from Sergei Trofimovich ---
(In reply to Martin Uecker from comment #6)
> Created attachment 56491 [details]
> patch
>
> Ok, let's try again...
The change fixes jemalloc and boehm-gc builds for me. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112347
--- Comment #2 from Sergei Trofimovich ---
A bit of debugging:
Program received signal SIGSEGV, Segmentation fault.
0x007bfff6 in convert_for_assignment (location=location@entry=263654,
expr_loc=expr_loc@entry=0,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112347
Sergei Trofimovich changed:
What|Removed |Added
CC||muecker at gwdg dot de
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112347
Bug ID: 112347
Summary: [14 regression] ICE on jemalloc-5.3.0: Segmentation
fault around convert_for_assignment()
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111653
Sergei Trofimovich changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112332
--- Comment #6 from Sergei Trofimovich ---
I confirm that the fix also fixes original python-3.11.6 build failure. Thank
you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112332
--- Comment #1 from Sergei Trofimovich ---
Slightly shorter example:
typedef union {
double d;
int L[2];
} U;
void d2b(int*);
void _Py_dg_dtoa(double dd) {
int be;
U u;
u.d = dd;
if (()->L[1])
d2b();
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112332
Bug ID: 112332
Summary: [14 regression] ICE: internal compiler error: in
extract_constrain_insn, at recog.cc:2705
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112321
Bug ID: 112321
Summary: [14 Regression] ICE during GIMPLE pass: dse: :
Segmentation fault
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
Sergei Trofimovich changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #8 from Sergei Trofimovich ---
bootstrap with default options did not fail for me either. I had to use
--enable-checking=release to trigger the failure. I wonder if it exposes the
failure for you as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #6 from Sergei Trofimovich ---
(In reply to Sergei Trofimovich from comment #5)
> Bisected down to r14-4943-g8d2130a4e5ce36 "[RA]: Modfify cost calculation
> for dealing with equivalences"
Sorry, pasted wrong hash. That should be a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
Sergei Trofimovich changed:
What|Removed |Added
CC||vmakarov at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #2 from Sergei Trofimovich ---
Reduced ira-build.cc down to the following:
// $ cat pp.cc.cc
typedef struct ira_object *ira_object_t;
struct ira_object {
void *conflicts_array;
int min, max;
};
void *ira_allocate(int);
int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #1 from Sergei Trofimovich ---
`diffoscope` says there is a difference in generated code in one of the
functions:
$ strip --strip-debug stage2-gcc-ira-build.o stage3-gcc-ira-build.o
$ diffoscope stage2-gcc-ira-build.o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
Bug ID: 112107
Summary: [14 Regression] bootstrap failure on i686-linux:
gcc/ira-build.o differs
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111824
--- Comment #2 from Sergei Trofimovich ---
Sounds good.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111824
Bug ID: 111824
Summary: [14 Regression] is invalid under
-U__STRICT_ANSI__ -std=c++11
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111663
Sergei Trofimovich changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |slyfox at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111283
Sergei Trofimovich changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111559
Sergei Trofimovich changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111663
--- Comment #1 from Sergei Trofimovich ---
Proposed the change as
https://gcc.gnu.org/pipermail/gcc-patches/2023-October/631790.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111663
Bug ID: 111663
Summary: profiledbootstrap fails on master:
gcc/genmodes.cc:2152:1: error:
‘gcc/build/genmodes.gcda’ profile count data file not
found
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
--- Comment #14 from Sergei Trofimovich ---
(In reply to Richard Sandiford from comment #13)
> Created attachment 56023 [details]
> Tentative fix
Re " That now triggers a warning
in some configurations, since the NUM_POLY_INT_COEFFS>1 tests
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111653
Bug ID: 111653
Summary: make bootstrap4 fails for -fchecking=2 code generation
changes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
Sergei Trofimovich changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
--- Comment #8 from Sergei Trofimovich ---
With https://gcc.gnu.org/PR111647#c1 I'm convinced it's a gcc's source code bug
and we should not try to write calls like `poly_int<1, T>(1, 1)` with
mismatching arity.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111647
--- Comment #1 from Sergei Trofimovich ---
More realistic example extracted from gcc's poly_int:
// $ cat rtl-tests.cc
template struct poly_int {
template constexpr poly_int (const Cs &... cs)
: coeffs { cs... } {}
int coeffs[N];
};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
--- Comment #7 from Sergei Trofimovich ---
If I try to build the file with `clang++-16` I'm getting the following error:
In file included from /home/slyfox/dev/git/gcc/gcc/rtl-tests.cc:22:
In file included from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
Sergei Trofimovich changed:
What|Removed |Added
Depends on||111647
--- Comment #6 from Sergei
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111647
Bug ID: 111647
Summary: g++ accepts different c++ on -fchecking= anf
checking=2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
--- Comment #5 from Sergei Trofimovich ---
The default value is `-fchecking=2` there. `-fchecking=0` and `-fchecking=1`
work fine. This means `-fchecking=` slightly alters c++ template instantiation.
I'll try to extract smaller example.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
--- Comment #4 from Sergei Trofimovich ---
Looks like `-fchecking=1` and `-fno-checking` handle c++ a bit differently.
Two commands differing only in `-fno-checking`. One works, one does not:
```
$ /tmp/gb/./prev-gcc/xg++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
Sergei Trofimovich changed:
What|Removed |Added
Summary|[14 Regression] |[14 Regression] bootstrap4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
--- Comment #1 from Sergei Trofimovich ---
Looks like this code is all under `#if CHECKING_P` of sorts. A few more
possibly affected entries:
```
$ git grep -P 'poly_int64 \(\d+, \d+\)'
gcc/config/riscv/riscv-selftests.cc:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
Bug ID: 111642
Summary: [14 Regression] profiledbootstrap failure:
poly-int.h:453:5: error: too many initializers for
‘long int [1]’ (possibly since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656
Bug 86656 depends on bug 111505, which changed state.
Bug 111505 Summary: [14 Regression] Asan (address-sanitizer) bootstrap fails
since r14-4003-geaa8e8541349df
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111505
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111505
Sergei Trofimovich changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
1 - 100 of 485 matches
Mail list logo
