https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117140
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117142
Richard Biener changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117145
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117146
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2024-10-15
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117148
--- Comment #3 from Andrew Pinski ---
(In reply to LIU Hao from comment #2)
>
> However it doesn't affect the bug. (https://godbolt.org/z/fdxbbadnj) It's
> because GCC fail to inline `atomic_load_iptr`. Forcing that function to be
> inlined wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117128
Davide Italiano changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
--- Comment #4 from David Malcolm ---
It's happening here:
(gdb) bt
#0 0x00f95395 in dump_function_name (pp=0x4d00c40
, t=, flags=148)
at ../../src/gcc/cp/error.cc:2139
#1 0x00f94109 in dump_function_decl (pp=0x4d00c40
, t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117159
Bug ID: 117159
Summary: kmovw storing to memory is assumed to zero-extend
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117145
Sam James changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114817
--- Comment #5 from Jonathan Wakely ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665537.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Bug ID: 117156
Summary: not applied option “-Wchanges-meaning”
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
Bug ID: 117157
Summary: changes-meaning is not in the index
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: documentation
Severity: normal
Priority: P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
--- Comment #2 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:11f0ea45b1b63ec7eb6a52179ca6fd4304e7e312
commit r15-4362-g11f0ea45b1b63ec7eb6a52179ca6fd4304e7e312
Author: Andrew Pinski
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117158
Bug ID: 117158
Summary: ICE with array access inside a template with a base
class
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117128
Sam James changed:
What|Removed |Added
Summary|[15 regression] GCC trunk |[15 regression] GCC trunk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108770
--- Comment #3 from qinzhao at gcc dot gnu.org ---
With my patch for new option -fdiagnostics-explain-harder, the output is:
t_108770.c: In function ‘init’:
t_108770.c:10:13: warning: array subscript 2 is above array bounds of ‘const
char *[2]’
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
--- Comment #2 from Jonathan Wakely ---
The post should say -Wno-changes-meaning disables it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #6 from Carlos Galvez ---
Alright reading Richard's comment I now understand he's not implying current
behavior is correct, but rather explaining why it happens. I take it then that
this is a bug in Clang then. Thanks for the clarifi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |MOVED
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117141
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
--- Comment #4 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:a72064c8c12f2cc3ab6fde7cd42f31f27193b5c4
commit r15-4363-ga72064c8c12f2cc3ab6fde7cd42f31f27193b5c4
Author: Andrew Pinski
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116510
--- Comment #12 from ak at gcc dot gnu.org ---
Like this? It fixes the test case.
I'm not sure why you want AND_EXPR, this is a truth formula. Maybe it should be
TRUTH_ANDIF_EXPR though to short circuit.
diff --git a/gcc/tree-if-conv.cc b/gcc/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
Bug ID: 117152
Summary: Segmentation fault in permerror(unsigned int, char
const*, ...)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116064
--- Comment #14 from Li Pan ---
> So you have to use one of those two.
Thanks, I see, let me update the config file and have another try.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116064
--- Comment #15 from Li Pan ---
(In reply to Li Pan from comment #14)
> > So you have to use one of those two.
>
> Thanks, I see, let me update the config file and have another try.
-Wno-error=template-body works, thanks a lot.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117153
Marek Polacek changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
Richard Biener changed:
What|Removed |Added
Version|unknown |15.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116064
Li Pan changed:
What|Removed |Added
CC||pan2.li at intel dot com
--- Comment #12 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
--- Comment #19 from John Paul Adrian Glaubitz ---
(In reply to Sam James from comment #18)
> See https://github.com/llvm/llvm-project/pull/111995 which fixes a problem
> that bisected to the same commit on ppc32.
Yes, I can confirm that this p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
Bug ID: 117155
Summary: Bogus -Wdangling-reference warning after
r13-3511-gd2249cd9adf
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80637
Jason Merrill changed:
What|Removed |Added
Resolution|--- |FIXED
Summary|constraint on a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
Bug 67491 depends on bug 80637, which changed state.
Bug 80637 Summary: [CWG2918] constraint on a member function does causes
ambigious and not allowing forming a pointer to the function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116876
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117022
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:50f27896adb272b40ab03a56fd192e74789bef97
commit r15-4369-g50f27896adb272b40ab03a56fd192e74789bef97
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117022
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115328
--- Comment #2 from Gaius Mulley ---
Created attachment 59353
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59353&action=edit
Proposed fix
Here is a proposed fix, which passes all regressions and implements the FORWARD
keyword. It also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117147
--- Comment #6 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:8af474aa5d5efdda7def6cdcec3f246df2c7026a
commit r15-4349-g8af474aa5d5efdda7def6cdcec3f246df2c7026a
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117137
--- Comment #5 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:79b881df72c946f2ba61879c36ae93b0cb974617
commit r15-4350-g79b881df72c946f2ba61879c36ae93b0cb974617
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #61 from Eric Botcazou ---
> Just a heads up, the minimal reproducer seems to be getting garbage movabsq
> instructions emitted again with the first stage gcc in the bootstrap phase
I cannot reproduce on the mainline though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117137
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117147
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117137
--- Comment #3 from Haochen Jiang ---
>From my bisect:
5977b746db3925aaba37722f5312419d5f2968a5 is the first bad commit
commit 5977b746db3925aaba37722f5312419d5f2968a5
Author: Richard Biener
Date: Tue Oct 8 09:01:01 2024 +0200
tree-opti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116749
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117137
Sam James changed:
What|Removed |Added
Summary|[15 Regression] ICE: in |[15 Regression] ICE: in
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117141
--- Comment #2 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:97f98855d4157a2511a713129ec77740fe6f88dc
commit r15-4354-g97f98855d4157a2511a713129ec77740fe6f88dc
Author: Pan Li
Date: Tue Oct 15 07:3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117153
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2024-10-15
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
Jonathan Wakely changed:
What|Removed |Added
Known to fail||15.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116064
--- Comment #13 from Tamar Christina ---
(In reply to Li Pan from comment #12)
> Looks RISC-V backend still has this issue, can you reproduce this?
>
> /opt/gcc-master//bin/g++ --version
> g++ (GCC) 15.0.0 20241014 (experimental)
>
> /opt/gcc-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117153
Bug ID: 117153
Summary: internal compiler error: Segmentation fault at
is_overloaded_fn(tree_node*)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
Jonathan Wakely changed:
What|Removed |Added
Summary|Segmentation fault in |[15 Regression]
|pe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
Jonathan Wakely changed:
What|Removed |Added
CC||dmalcolm at gcc dot gnu.org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117152
--- Comment #3 from Jonathan Wakely ---
The backtrace with locations is:
117152.cc:3:48: error: could not convert ‘{0}’ from ‘’ to ‘S&&’
3 | friend constexpr S::S(S&& = {0}) noexcept;
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117153
--- Comment #2 from Jonathan Wakely ---
The backtrace with locations is:
117153.cc: In instantiation of ‘void f() [with T = double]’:
117153.cc:10:25: required from here
117153.cc:8:5: internal compiler error: Segmentation fault
8 | d +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106201
Bug 106201 depends on bug 94894, which changed state.
Bug 94894 Summary: avoidable instantiation of conversion function template
during overload resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105766
Bug 105766 depends on bug 94894, which changed state.
Bug 94894 Summary: avoidable instantiation of conversion function template
during overload resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94894
Patrick Palka changed:
What|Removed |Added
Target Milestone|13.0|---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
Bug ID: 117154
Summary: Aggregate initialization with protected destructor in
Base class: GCC vs Clang difference
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #24 from Kamil Dudka ---
(In reply to David Malcolm from comment #21)
> (In reply to David Malcolm from comment #20)
> > How about another option
> > -fdiagnostics-set-output=
> > that would work like
> > -fdiagnostics-add-outpu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117138
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117147
--- Comment #8 from Andrew Pinski ---
Reduced testcase:
```
double Test(int p, double *sum3, double *sum4, double *wX) {
double tmp;
double bS1 = 0.;
double bS2 = 0.;
for (int i = 0; i < p; ++i) {
tmp = wX[i] * wX[i];
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117151
Bug ID: 117151
Summary: _GLIBCXX_USE_C99_COMPLEX_ARC and
_GLIBCXX_USE_C99_COMPLEX are not defined in a
consistent way
Product: gcc
Version: 14.0
Stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #62 from Julian Waters ---
That's gonna be a problem, sigh. The only noteworthy difference I can see
between the 2 patches that is related to the secrel32 unspec is one of the
GET_CODE == SYMBOL_REF is enclosed in brackets. Unless thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #63 from Julian Waters ---
(I know the predicates have been brought up as a potential cause for this, but
if it cannot be replicated with the candidate patch the problem may lie
elsewhere)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117116
--- Comment #14 from Uroš Bizjak ---
(In reply to Hongtao Liu from comment #13)
> > I tried to split V2SImode CONST_VECTOR to two SImode CONST elements, but
> > there were some further ICEs generated, and it is getting a bit late
> > here...?
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117149
--- Comment #2 from Andrew Pinski ---
Also the GCC you are using defaults to using -fstack-protector by default so it
is not a bug in the normal releases of GCC.
See
https://gcc.gnu.org/onlinedocs/gcc-14.2.0/gcc/x86-Options.html#index-mstack-pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116506
Iain Sandoe changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117136
Thomas Schwinge changed:
What|Removed |Added
Resolution|--- |FIXED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117140
Tamar Christina changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117140
--- Comment #6 from Tamar Christina ---
Ok, mine then.
It looks like it's this loop:
int n_3_TYPE1_int64_t = 32;
int32_t x_3_int32_t = 233;
int32_t x2_3_int32_t = 78;
int64_t y_3_int64_t = 1234;
int32_t f_3_int32_t[33 * 2 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117147
--- Comment #9 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:1aac888fac6cff63a3d6522bcf9b8439e14320ad
commit r15-4352-g1aac888fac6cff63a3d6522bcf9b8439e14320ad
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #1 from Jonathan Wakely ---
This is https://wg21.link/cwg2244 and it looks like GCC already implements the
suggested resolution.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83417
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106676
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
--- Comment #3 from Dimitry Andric ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Dimitry Andric from comment #0)
> > After r15-3941-g2531f014fb2364 ("c++: Implement -Wdangling-reference
>
> I think the correct commit is
> r13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106676
--- Comment #14 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:7f65f94917866c6b18d9698eec6451c1bf21e0f9
commit r15-4356-g7f65f94917866c6b18d9698eec6451c1bf21e0f9
Author: Jonathan Wakely
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
--- Comment #1 from Jonathan Wakely ---
(In reply to Dimitry Andric from comment #0)
> After r15-3941-g2531f014fb2364 ("c++: Implement -Wdangling-reference
I think the correct commit is
r13-3511-gd2249cd9adf5ae638577139177a50f7e62d8abd9
> [PR1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
--- Comment #2 from Jonathan Wakely ---
(In reply to Dimitry Andric from comment #0)
> Clearly, there is no dangling reference here, and not even a temporary. And
> even if there was a temporary, its lifetime should have been extended.
No, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84884
Andrew Pinski changed:
What|Removed |Added
CC||carlosgalvezp at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84884
--- Comment #2 from Andrew Pinski ---
https://wg21.link/cwg2244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84884
Andrew Pinski changed:
What|Removed |Added
See Also||https://github.com/llvm/llv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117142
Sam James changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
Summ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97088
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117150
Bug ID: 117150
Summary: mstack-protector-guard-symbol= is not documented
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: documentation
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117137
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114052
--- Comment #12 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #11)
> Note I don't get an __builtin_unreachable() in GCC 14.1.0 nor 13.1.0.
I have no idea what I was thinking when I wrote this as I just retested and it
fails wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116749
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117151
--- Comment #1 from Jonathan Wakely ---
(In reply to vincenzo Innocente from comment #0)
> Not sure if it is intended or not but
> if _GLIBCXX_USE_C99_COMPLEX is defined to be "0" (say on the command line)
That's undefined behaviour, it's an in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #65 from Eric Botcazou ---
> Just tried it again, it emits broken assembly on both master and gcc 14 with
> the "Latest TLS" patch
What command line do you use to compile the minimal reproducer?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #66 from Eric Botcazou ---
> That's gonna be a problem, sigh. The only noteworthy difference I can see
> between the 2 patches that is related to the secrel32 unspec is one of the
> GET_CODE == SYMBOL_REF is enclosed in brackets. Unle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117136
--- Comment #3 from GCC Commits ---
The trunk branch has been updated by Thomas Schwinge :
https://gcc.gnu.org/g:fa90febea9801d4255bf6a1e9f0fd998629c3c7c
commit r15-4348-gfa90febea9801d4255bf6a1e9f0fd998629c3c7c
Author: Thomas Schwinge
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117138
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117110
--- Comment #8 from Simon Martin ---
FWIW I can confirm that the build is restored on Darwin. Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117110
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116921
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116898
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116899
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44952
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #64 from Julian Waters ---
Just tried it again, it emits broken assembly on both master and gcc 14 with
the "Latest TLS" patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116749
--- Comment #6 from Sam James ---
(In reply to Sam James from comment #5)
> r14-2709-g65ff4a45b11b5a was the fix on 14...
and made it latent. It crashes on trunk with -fno-tree-ch.
1 - 100 of 172 matches
Mail list logo