https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112421
Bug ID: 112421
Summary: GCC emits warning potential null dereference
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112420
Bug ID: 112420
Summary: Unexpected vectorization for RISC-V
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112399
JuzheZhong changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112399
--- Comment #1 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:f1e084c6c3ef1d1233e35823dacfdf9cee722430
commit r14-5179-gf1e084c6c3ef1d1233e35823dacfdf9cee722430
Author: Juzhe-Zhong
Date: Mon Nov 6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105558
--- Comment #8 from Thomas Koenig ---
(In reply to Andrew Pinski from comment #6)
> Would be interesting to find what patch broke this and what patch fixed the
> -mtune=generic case.
It is not easy bisecting with old compilers - compilation iss
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112419
uecker at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112419
Bug ID: 112419
Summary: [14 Regression] gcc.dg/Wnonnull-4.c excess error for
32-bit targets
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112382
--- Comment #2 from Andrew Pinski ---
(In reply to Richard Biener from comment #1)
> Note ((~b&a)>>shift) & 1 is two more GIMPLE ops than (a&b) != a so I'd
> expect the reverse transform on GIMPLE and maybe target specific expansion
> tweaks (or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112402
--- Comment #2 from Andrew Pinski ---
The orginal threads about patch splitting:
https://gcc.gnu.org/legacy-ml/gcc/2015-03/msg00057.html
https://gcc.gnu.org/pipermail/gcc/2015-May/217495.html
> or axe path splitting or move it to RTL
Jeff had a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015
--- Comment #9 from Andrew Pinski ---
I should note that PR 112416 is not needed to vectorize the loop, though it
would improve code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015
Andrew Pinski changed:
What|Removed |Added
Depends on||112418
--- Comment #8 from Andrew Pinsk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112418
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-11-07
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112418
Bug ID: 112418
Summary: factor_out_conditional_operation could be done for
more phis
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimizati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112417
HaoChen Gui changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |guihaoc at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111907
--- Comment #6 from Haochen Jiang ---
Proposed patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635410.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112417
Bug ID: 112417
Summary: expand_builtin_return shoud check alignment for the
memory reference
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112340
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2023-11-07
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015
Andrew Pinski changed:
What|Removed |Added
Depends on||112416
--- Comment #6 from Andrew Pinsk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112416
Bug ID: 112416
Summary: absu is not detected
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015
--- Comment #5 from Andrew Pinski ---
After fixing PR 112324 (and a secondary patch to phiopt to do
factor_out_conditional_operation for all phi nodes rather than just a single
one) we still miss the abs detection:
_34 = tmp_24 < 0;
_55 = (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263
--- Comment #17 from Jonathan Wakely ---
Thanks, Ian!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #10 from dave.anglin at bell dot net ---
On 2023-11-06 5:49 p.m., sjames at gcc dot gnu.org wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x412083f0 in _PyST_GetSymbol (name=0xf9a34a00, ste=) at
> Python/symtable.c:3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263
Ian Lance Taylor changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315
--- Comment #10 from CVS Commits ---
The releases/gcc-12 branch has been updated by Ian Lance Taylor
:
https://gcc.gnu.org/g:56909c9d4842925749cd9e061ef4afa0501f85e9
commit r12-9961-g56909c9d4842925749cd9e061ef4afa0501f85e9
Author: Ian Lance T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263
--- Comment #15 from CVS Commits ---
The releases/gcc-12 branch has been updated by Ian Lance Taylor
:
https://gcc.gnu.org/g:56909c9d4842925749cd9e061ef4afa0501f85e9
commit r12-9961-g56909c9d4842925749cd9e061ef4afa0501f85e9
Author: Ian Lance T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263
--- Comment #14 from CVS Commits ---
The releases/gcc-13 branch has been updated by Ian Lance Taylor
:
https://gcc.gnu.org/g:8484e3479fe80aebdc4a2406473aef906055b4f8
commit r13-8006-g8484e3479fe80aebdc4a2406473aef906055b4f8
Author: Ian Lance T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315
--- Comment #9 from CVS Commits ---
The releases/gcc-13 branch has been updated by Ian Lance Taylor
:
https://gcc.gnu.org/g:8484e3479fe80aebdc4a2406473aef906055b4f8
commit r13-8006-g8484e3479fe80aebdc4a2406473aef906055b4f8
Author: Ian Lance Ta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263
--- Comment #13 from CVS Commits ---
The master branch has been updated by Ian Lance Taylor :
https://gcc.gnu.org/g:2b64e4a54042fb8f75f1c1429eb1c13afb9fa118
commit r14-5173-g2b64e4a54042fb8f75f1c1429eb1c13afb9fa118
Author: Ian Lance Taylor
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315
--- Comment #8 from CVS Commits ---
The master branch has been updated by Ian Lance Taylor :
https://gcc.gnu.org/g:2b64e4a54042fb8f75f1c1429eb1c13afb9fa118
commit r14-5173-g2b64e4a54042fb8f75f1c1429eb1c13afb9fa118
Author: Ian Lance Taylor
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #9 from Sam James ---
I think the key object is Python/compile.o, but not certain yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #8 from Sam James ---
(In reply to Jeffrey A. Law from comment #6)
Program received signal SIGSEGV, Segmentation fault.
0x412083f0 in _PyST_GetSymbol (name=0xf9a34a00, ste=) at
Python/symtable.c:396
396 PyObject *v = PyDict_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #7 from dave.anglin at bell dot net ---
On 2023-11-06 5:20 p.m., law at gcc dot gnu.org wrote:
> The biggest concern I'd have with f-m-o on the PA would be the
> implicit segment selection that happens on the base register -- but it w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #6 from Jeffrey A. Law ---
Do we have assembly code around the faulting point (x/20i $pc) and a register
dump (i r)? The biggest concern I'd have with f-m-o on the PA would be the
implicit segment selection that happens on the base
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
Sam James changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #5 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #4 from Sam James ---
Created attachment 56520
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56520&action=edit
list_of_differing_files.txt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
--- Comment #32 from JuzheZhong ---
26% time reduction seems not enough.
Maybe we still need to optimize MD patterns to fix this issue ?
But I have no idea to optimize it since I already tried my best to reduce
them.
According to RVV intrinsic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106511
--- Comment #7 from Andrew Macleod ---
(In reply to Richard Biener from comment #2)
> VRP could use max_stmt_executions here (note it doesn't properly handle loop
> nests so the name is somewhat misleading)
Given some arbitrary statement S, how
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #3 from dave.anglin at bell dot net ---
On 2023-11-06 4:00 p.m., sjames at gcc dot gnu.org wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x412083fc in _PyST_GetSymbol (name=0xf9a33a60, ste=) at
> Python/symtable.c:39
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #2 from Sam James ---
I'll grab a bad vs good build directory next and upload both, and then try see
which objects differ.
Dave, can you reproduce?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
Sam James changed:
What|Removed |Added
Summary|[14 regression] Python 3.11 |[14 regression] Python 3.11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
Bug ID: 112415
Summary: [14 regression] Python 3.11 miscompiled with new RTL
fold mem offset pass, since r14-4664-g04c9cf5c786b94
Product: gcc
Version: 14.0
Status: UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104819
--- Comment #3 from anlauf at gcc dot gnu.org ---
Created attachment 56519
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56519&action=edit
Partial patch
This patch adjusts the checking so that nested NULL()s are accepted,
tries to impleme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413
--- Comment #3 from Vincent Riviere ---
(In reply to Andrew Pinski from comment #1)
> I don't see any issues with the output of gcc. Are you sure this is not a
> binutils gnu as issue where the offsets are done incorrectly there.
Yes, I'm sure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111472
--- Comment #5 from Andrew Pinski ---
(In reply to Andrew Macleod from comment #3)
> I'm not sure that this didn't uncover something elsewhere, possibly ivopts
> since that pass seems to be generating something different and I think there
> were
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111472
--- Comment #4 from Andrew Macleod ---
(In reply to Andrew Macleod from comment #3)
> I'm not sure that this didn't uncover something elsewhere, possibly ivopts
> since that pass seems to be generating something different and I think there
> wer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104819
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-11-06
Statu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111472
--- Comment #3 from Andrew Macleod ---
I'm not sure that this didn't uncover something elsewhere, possibly ivopts
since that pass seems to be generating something different and I think there
were some fixes put in there on trunk?.
Regardless, t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112324
--- Comment #5 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Andrew Pinski from comment #3)
> > Note a simple patch to improve phiopt here does not improve the original
> > code in openjpeg.
> >
> > The reaso
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112414
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112414
Bug ID: 112414
Summary: Does gcc need __builtin_assume_separate_storage?
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413
--- Comment #2 from Vincent Riviere ---
Cause is in gcc/config/m68k/linux.h, macro ASM_RETURN_CASE_JUMP:
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/m68k/linux.h;h=2e1cb5498b86f053d1e9b7c530648dfa186ca4c4;hb=HEAD#l96
jmp %%pc@(2,%0:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413
Andrew Pinski changed:
What|Removed |Added
Component|c |target
--- Comment #1 from Andrew Pinsk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413
Bug ID: 112413
Summary: Wrong switch jump table offset
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112412
Bug ID: 112412
Summary: Masked reduction functions return an unallocated array
when the result is empty
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110551
--- Comment #9 from Moncef Mechri ---
With Roger's latest patch, codegen looks good with -O2 and -O2 -march=haswell.
Thanks!
I think this can be marked as resolved?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109684
--- Comment #25 from Steve Kargl ---
On Mon, Nov 06, 2023 at 03:34:42PM +, trnka at scm dot com wrote:
> > If expr->where is pointing to NULL, then something is definitely not
> > set up correctly or your code is now going through a differen
gcc-trunk//binary-trunk-r14-5141-20231106022717-g1a55724f787-checking-yes-rtl-df-extra-powerpc64le
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231106 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65833
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
--- Comment #31 from Andreas Schwab ---
For the first time the bootstrap time has been reduced, from 192543 (20231028)
to 141231 (20231103), -26,6%.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112324
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> Note a simple patch to improve phiopt here does not improve the original
> code in openjpeg.
>
> The reason why is due to the code in phiopt here is only operat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
--- Comment #7 from Frediano Ziglio ---
Sorry for the noise, thanks for the informations.
I didn't notice banner on top. I went back and I notice it, pretty small and it
looks like a lot of other website banners for technical disruptions or coo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112324
--- Comment #3 from Andrew Pinski ---
Note a simple patch to improve phiopt here does not improve the original code
in openjpeg.
The reason why is due to the code in phiopt here is only operates on the case
where the phi would be the only one.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108409
Mike Crowe changed:
What|Removed |Added
CC||mac at mcrowe dot com
--- Comment #7 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112408
--- Comment #3 from ibuclaw at gcc dot gnu.org ---
Based on what I see here, this patch to core.cpuid should be sufficient to fix
loop and not introduce any change in existing behaviour.
---
--- a/druntime/src/core/cpuid.d
+++ b/druntime/src/cor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
--- Comment #2 from Andrew Pinski ---
Confirmed.
Looks like GCC is messing the Most vexing parse here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
Marek Polacek changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
Bug ID: 112410
Summary: error when auto(x) is used in a variable initializer
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112397
Iain Sandoe changed:
What|Removed |Added
Component|libstdc++ |target
--- Comment #2 from Iain Sandoe -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
Frediano Ziglio changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111572
--- Comment #6 from Martin Jambor ---
(In reply to Andrew Pinski from comment #5)
> Hmm, this works on the trunk now. Would be a good idea to figure out what
> "fixed" it.
If my simple test is correct, the error disappeared with
r14-4790-g96923
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
--- Comment #3 from Jonathan Wakely ---
(In reply to Frediano Ziglio from comment #0)
> static unsigned
> cksum(const void *pkt, size_t len, unsigned int start)
> {
> const uint16_t *data = (const uint16_t *) pkt;
> unsigned sum = st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
--- Comment #2 from Andrew Pinski ---
I have to double check but I am 99% sure this code is undefined due to alias
violations.
Use either memcpy or -fno-strict-aliasing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #1 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112409
Bug ID: 112409
Summary: Structure is not initialized as expected
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112408
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #1 from ibuclaw at gcc dot gnu.org ---
> (In reply to Rainer Orth from comment #0)
>> This affects all DMD-based versions of GDC, while the previous C++-based
>> versions
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112408
ibuclaw at gcc dot gnu.org changed:
What|Removed |Added
CC||ibuclaw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112408
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112408
Bug ID: 112408
Summary: [12/13/14 regression] d21 loops in getCpuInfo0B in
Solaris/x86 kernel zone
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50755
--- Comment #5 from Georg-Johann Lay ---
(In reply to Roger Sayle from comment #4)
> This appears to be fixed on mainline.
At least the test case passes on newer versions. For a definite answer you'd
have to bisect / find the patch that solved
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109684
--- Comment #24 from Tomáš Trnka ---
(In reply to Steve Kargl from comment #23)
> If expr->where is pointing to NULL, then something is definitely not
> set up correctly or your code is now going through a different code
> path in the compiler.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112407
--- Comment #1 from Tomáš Trnka ---
Created attachment 56516
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56516&action=edit
Hacky patch working around the issue on this testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112407
Bug ID: 112407
Summary: [13 Regression] Fix for PR37336 triggers an ICE in
gfc_format_decoder while constructing a vtab
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954
--- Comment #7 from CVS Commits ---
The master branch has been updated by Joseph Myers :
https://gcc.gnu.org/g:fad61bf73b3158157a136bf4d9373fc3d9afe319
commit r14-5160-gfad61bf73b3158157a136bf4d9373fc3d9afe319
Author: Joseph Myers
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112393
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112405
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112405
--- Comment #2 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:9125969086bfa1bf804b246ea574a2329b06d2c5
commit r14-5158-g9125969086bfa1bf804b246ea574a2329b06d2c5
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111950
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111000
Bug 111000 depends on bug 111950, which changed state.
Bug 111950 Summary: [14 Regression] ICE in compute_live_loop_exits, at
tree-ssa-loop-manip.cc:250 since r14-4786-gd118738e71c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111950
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112405
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
L
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110641
Jan Hubicka changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from Jan Hubicka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111950
--- Comment #11 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:bf72d50d16f0c1fa8102ca2544d2a05772f8c273
commit r14-5155-gbf72d50d16f0c1fa8102ca2544d2a05772f8c273
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112406
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
--- Comment #1 from Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112404
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112404
--- Comment #4 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:3cc9ad41db87fb85b13a56bff1f930c258542a70
commit r14-5154-g3cc9ad41db87fb85b13a56bff1f930c258542a70
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110859
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
1 - 100 of 136 matches
Mail list logo
