https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112871
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112872
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112875
Richard Biener changed:
What|Removed |Added
CC||vmakarov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41201
Gwenole Beauchesne changed:
What|Removed |Added
CC||gb.devel at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48026
Gwenole Beauchesne changed:
What|Removed |Added
CC||gb.devel at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41201
Sam James changed:
What|Removed |Added
Depends on||87299
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41201
Sam James changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48026
Bug 48026 depends on bug 41201, which changed state.
Bug 41201 Summary: #pragma GCC target ("sse2") doesn't alter __SSE2__ in C++
(as it does in C)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41201
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48026
--- Comment #6 from Sam James ---
(In reply to Gwenole Beauchesne from comment #5)
> Created attachment 56811 [details]
> Proposed patch against trunk
>
> Here is a proposed patch against trunk, which includes a fix for PR
> preprocessor/87299 (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87299
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112868
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #4 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87299
--- Comment #8 from Gwenole Beauchesne ---
Hi, can you please consider a backport to GCC 13 branch? The patch applies
cleanly as is, but causes regressions that are further fixed with e45c564e (for
PR pch/112319).
GCC 13 is the first and most co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112876
Bug ID: 112876
Summary: rangesc.end() is unnecessarily assigned by the return
value of c.emplace()
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112876
康桓瑋 changed:
What|Removed |Added
Summary|rangesc.end() is|ranges:to: c.end() is
|unnecess
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112876
--- Comment #2 from 康桓瑋 ---
I believe the above is well-formed after LWG 4016.
In addition, container-appendable requires `c.emplace(c.end(), *it)` to be
well-formed but `auto end = c.end(); c.emplace(end, *it);` may not be.
Sorry for the ped
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112872
--- Comment #2 from Robin Dapp ---
Thanks. Yes that's similar and also looks fixed by the introduction of the
vec_init expander. Added this test case to the patch and will push it soon.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106511
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112809
--- Comment #3 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:0ca64f846edce3c7b7f26bcc5978118e560e65b1
commit r14-6209-g0ca64f846edce3c7b7f26bcc5978118e560e65b1
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112760
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:e44ed92dbbe9d4e5c23f486cd2f77a6f9ee513c5
commit r14-6210-ge44ed92dbbe9d4e5c23f486cd2f77a6f9ee513c5
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112809
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112760
--- Comment #7 from Jakub Jelinek ---
This is now latent, we need to decide about the updating and usability of
REG_UNUSED notes, but after moving the pass it shouldn't trigger on this
testcase.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112572
--- Comment #33 from Jakub Jelinek ---
This should be now hopefully latent after
r14-6210-ge44ed92dbbe9d4e5c23f486cd2f77a6f9ee513c5, we need to decide about the
updating and usability of REG_UNUSED notes, but after moving the pass it
shouldn't t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112877
Bug ID: 112877
Summary: TARGET_PROMOTE_PROTOTYPES is not honored consistently,
should maybe not apply to builtins
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88345
Jan Hubicka changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
Romain Geissler changed:
What|Removed |Added
CC||romain.geissler at amadeus dot
com
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112872
--- Comment #3 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:056cce412862f8d9b56a40dfbcbc3f9fa7f92883
commit r14-6211-g056cce412862f8d9b56a40dfbcbc3f9fa7f92883
Author: Robin Dapp
Date: Tue Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112854
--- Comment #4 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:056cce412862f8d9b56a40dfbcbc3f9fa7f92883
commit r14-6211-g056cce412862f8d9b56a40dfbcbc3f9fa7f92883
Author: Robin Dapp
Date: Tue Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112853
--- Comment #8 from Robin Dapp ---
With Juzhe's latest fix that disables VLS modes >= 128 bit for zvl128b x264
runs without issues here and some of the additional execution failures are
gone.
Will post the current comparison later.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
--- Comment #24 from Richard Biener ---
The bug wasn't about uninit diagnostics with ASAN but without. There are
plenty of diagnostic "bugs" when sanitizing is enabled and those are really
hard to fix since plenty of diagnostics rely on optimiz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89618
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
--- Comment #25 from Romain Geissler ---
So it means we should rather go for "silencing" workaround from comment #19 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98673
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
--- Comment #26 from rguenther at suse dot de ---
On Wed, 6 Dec 2023, romain.geissler at amadeus dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
>
> --- Comment #25 from Romain Geissler ---
> So it means we should rather
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
Bug 24639 depends on bug 106722, which changed state.
Bug 106722 Summary: bogus uninit warning in tree-vect-loop-manip.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
--- Comment #27 from Jakub Jelinek ---
That is just a very partial solution. As mentioned in lots of other
bugreports, one should simply ignore or take with a grain of salt warnings
from the instrumented builds (whether it is -fsanitize=undefi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112878
Bug ID: 112878
Summary: ICE: in ctf_add_slice, at ctfc.cc:499 with -std=c23
-gctf1
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289
Thomas Schwinge changed:
What|Removed |Added
CC||burnus at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112879
Bug ID: 112879
Summary: [14 Regression] 4% exec time regression of 525.x264_r
on AMD Zen4
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: needs-bisect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
--- Comment #28 from Romain Geissler ---
Ok it's clear. I haven't really played yet with sanitizers, I didn't know it
had these well known "issue" with creating more middle end false positive
warnings (I am used to them in LTO mode).
So I will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #29 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289
--- Comment #9 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:d7ceffab96ecd021d3e869dff33d0ad4b8577c4f
commit r14-6218-gd7ceffab96ecd021d3e869dff33d0ad4b8577c4f
Author: Jakub Jelinek
Date: W
in/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-6210-20231206095912-ge44ed92dbbe-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231206 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112879
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112858
--- Comment #5 from Thomas Schwinge ---
(I did see that the '__cxa_thread_atexit_impl' issue has been resolved
differently, but there is a genuine GCC/nvptx issue here.)
(In reply to myself from comment #1)
> Indeed in 'build-gcc/nvptx-none/lib
ecking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231206 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112879
--- Comment #2 from Hongtao Liu ---
(In reply to Richard Biener from comment #1)
> Possibly the reduc_* support in the backend now BB vectorizes unprofitable
> cases.
maybe zmm reduction, and we should have reasonable cost for reduction
vec_to_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112834
Paul Thomas changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112834
Paul Thomas changed:
What|Removed |Added
Blocks||87477
--- Comment #2 from Paul Thomas --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289
Thomas Schwinge changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112762
--- Comment #6 from GCC Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:e0eca4a55bd14d506708fb0396b31e7f7383160c
commit r14-6220-ge0eca4a55bd14d506708fb0396b31e7f7383160c
Author: Marek Polacek
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112726
--- Comment #1 from Giuliano Procida ---
Much of the initial report can be ignored, `llvm-dwarfdump` is buggy for DWARF
5 before version 15.
Here's a much simpler statement:
gcc -gdwarf-5 -fdebug-prefix-map=$(pwd)= -c foo.c is broken and the p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112762
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112762
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88345
--- Comment #19 from Michael Matz ---
(In reply to Jan Hubicka from comment #18)
> Reading all the discussion again, I am leaning towards -falign-all-functions
> + documentation update explaining that -falign-functions/-falign-loops are
> optimiz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53499
--- Comment #5 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:c1e54c82a9e1855499ef7bb8827540e6a097532b
commit r14-6221-gc1e54c82a9e1855499ef7bb8827540e6a097532b
Author: Jason Merrill
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109536
Jonathan Wakely changed:
What|Removed |Added
Keywords||patch
--- Comment #4 from Jonathan Wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112855
--- Comment #2 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:c9d5b46a25547035e381b0246de5cb553ca8b02d
commit r14-6222-gc9d5b46a25547035e381b0246de5cb553ca8b02d
Author: Juzhe-Zhong
Date: Wed Dec 6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112832
--- Comment #3 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:d40796e3813fdf646ca7b7ce9630d5cc121353b4
commit r13-8130-gd40796e3813fdf646ca7b7ce9630d5cc121353b4
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110133
--- Comment #4 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:ca233ac9ba085e2acd385bda6a778684a0c96694
commit r13-8129-gca233ac9ba085e2acd385bda6a778684a0c96694
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112473
--- Comment #5 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:f6ed5e0715da7040b04c465424bb33fcb95a5c20
commit r13-8131-gf6ed5e0715da7040b04c465424bb33fcb95a5c20
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112480
--- Comment #10 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:866870c51d58881819db6db76dcdfe3f43d89903
commit r13-8132-g866870c51d58881819db6db76dcdfe3f43d89903
Author: Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111948
--- Comment #10 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:be26992b3115b95189ac02fcf25902cb5430c0e1
commit r13-8133-gbe26992b3115b95189ac02fcf25902cb5430c0e1
Author: Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110133
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112832
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111948
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112480
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112477
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2023-12-06
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
Bug ID: 112882
Summary: [14 Regression] std::clamp no longer usable in header
only mode
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110639
--- Comment #4 from Tobias Burnus ---
There are *two* independent issues:
(A) Predefined firstprivate does not find mappings done in the same
directive, e.g.
int a[100];
int *p = &a[0];
#pragma omp target teams distribute map(a)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112737
John David Anglin changed:
What|Removed |Added
CC||danglin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98531
--- Comment #20 from John David Anglin ---
The fails have changed on hppa with gcc-14 trunk:
FAIL: g++.dg/modules/xtreme-header-2_c.C -std=c++2b (test for excess errors)
Excess errors:
/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/includ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112883
Bug ID: 112883
Summary: FAIL: g++.dg/modules/xtreme-header-2_c.C -std=c++2b
(test for excess errors)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112880
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2023-12-06
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112314
--- Comment #9 from GCC Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:c5c57aa7e63da2e769f4fda6e2ec9e8bd0c7b344
commit r12-10029-gc5c57aa7e63da2e769f4fda6e2ec9e8bd0c7b344
Author: Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112881
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2023-12-06
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112884
Bug ID: 112884
Summary: Missing optimization: fold a%2==0 ? a/2*2 : 0 to
a%2==0 ? a : 0
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112445
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111965
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
--- Comment #2 from Jonathan Wakely ---
That change was broken anyway: when _GLIBCXX_ASSERTIONS was not defined, the
condition in the assertion is if constexpr (is_constant_evaluated()) which is
always true, even when not actually doing constant
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
Jonathan Wakely changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88345
--- Comment #20 from Jan Hubicka ---
>
> Live patching (user-space) doesn't depend on any particular alignment of
> functions, on x86-64 at least. (The plan for other architectures wouldn't
> need
> any specific alignment either). Note that t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
--- Comment #3 from Jonathan Wakely ---
This minimal fix is enough to remove the reference to __glibcxx_assert_fail
when optimization is enabled (at any level):
--- a/libstdc++-v3/include/bits/c++config
+++ b/libstdc++-v3/include/bits/c++config
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112885
Bug ID: 112885
Summary: FAIL: gcc.dg/tree-ssa/ssa-sink-16.c (internal compiler
error: Segmentation fault )
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112411
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88345
--- Comment #21 from Michael Matz ---
(In reply to Jan Hubicka from comment #20)
> >
> > Live patching (user-space) doesn't depend on any particular alignment of
> > functions, on x86-64 at least. (The plan for other architectures wouldn't
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112885
--- Comment #1 from Andrew Pinski ---
I suspect this is already fixed with r14-6132 (aka PR 112848 ).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112411
Jakub Jelinek changed:
What|Removed |Added
CC||vmakarov at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112572
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40209
Andrew Pinski changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112886
Bug ID: 112886
Summary: We need a new print_operand output modifier for vector
double
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112760
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40209
Andrew Pinski changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment #9 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40209
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112884
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112411
--- Comment #9 from Jakub Jelinek ---
If we wanted to support just INSN_UIDs up to 0x5554, it could be even just
lra_insn_recog_data_len = index * 3U / 2 + 1;
Looking around, vec.cc has similar limitation, it uses unsigned rather than int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112855
Patrick O'Neill changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112872
Patrick O'Neill changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
1 - 100 of 163 matches
Mail list logo