https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109696
--- Comment #4 from Jakub Jelinek ---
r14-458-g2b8a27634f5d28e3e7c4a08bf065f2daada7aed2 fixed it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112372
Richard Biener changed:
What|Removed |Added
Component|debug |ipa
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112382
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
--- Comment #1 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112370
--- Comment #2 from Alexander Grund ---
FWIW: I tried to run cvise on this however it created an invalid example where
indeed a non-heap pointer would be freed. I'll attach it anyway for reference
as it took hours to run the reduce
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112370
--- Comment #3 from Alexander Grund ---
Created attachment 56513
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56513&action=edit
INVALID reduced example (after running cvise on the former example)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112384
Richard Biener changed:
What|Removed |Added
Target|aarch64 |aarch64, x86_64-*-*
Ever confirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112387
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112402
--- Comment #1 from Richard Biener ---
So the question is whether we should do more if-conversion on GIMPLE then (or
axe path splitting or move it to RTL)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112369
--- Comment #9 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:d803438e0c4016aff720fad418377c5b13567063
commit r14-5145-gd803438e0c4016aff720fad418377c5b13567063
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112367
--- Comment #7 from Paul Zimmermann ---
thank you all and sorry for the noise
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112369
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112397
Jonathan Wakely changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112361
--- Comment #6 from Robin Dapp ---
So "before" we created
vect__3.12_55 = MEM [(float *)vectp_a.10_53];
vect__ifc__43.13_57 = VEC_COND_EXPR ;
// _ifc__43 = _24 ? _3 : 0.0;
stmp__44.14_58 = BIT_FIELD_REF ;
stmp__44.14_59 = r3_29 + stmp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111950
Richard Biener changed:
What|Removed |Added
Attachment #56502|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112351
--- Comment #1 from Richard Biener ---
The question is also how much of explicit thread safety is needed when the init
is now happening inside libstdc++ (thus from _init which should be already
ensured to execute exactly once)? Is that (_init t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112361
--- Comment #7 from rguenther at suse dot de ---
On Mon, 6 Nov 2023, rdapp at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112361
>
> --- Comment #6 from Robin Dapp ---
> So "before" we created
>
> vect__3.12_55 =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112377
--- Comment #3 from Jonathan Wakely ---
(In reply to David Binderman from comment #0)
> I think that should be enough to implement the new warning for C++.
Certainly not. Apart from the fact that there's a lot more needed than just
making the o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111720
--- Comment #28 from Richard Biener ---
I tried to look up the requirements of __riscv_vle8_v_u8m2 in the vector
intrinsic specs but besides listing all those intrinsics the spec doesn't
contain _any_ documentation? The 2nd arg is named 'vl' wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112393
--- Comment #4 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:f463ef79ddb403570461343ebda0c1aeac85d5bb
commit r14-5147-gf463ef79ddb403570461343ebda0c1aeac85d5bb
Author: liuhongt
Date: Mon Nov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112393
--- Comment #5 from Hongtao.liu ---
Fixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364
--- Comment #12 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:17df6ddcf11aef6d200305d35641a7deb2f430e1
commit r14-5148-g17df6ddcf11aef6d200305d35641a7deb2f430e1
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111720
--- Comment #29 from JuzheZhong ---
(In reply to Richard Biener from comment #28)
> I tried to look up the requirements of __riscv_vle8_v_u8m2 in the vector
> intrinsic specs but besides listing all those intrinsics the spec doesn't
> contain _a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112404
Bug ID: 112404
Summary: [14 Regression] 521.wrf_r fails to build with internal
compiler error: in get_vectype_for_scalar_type, at
tree-vect-stmts.cc:13311
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112351
--- Comment #2 from Jonathan Wakely ---
Ah yes, that's a good point. Patrick's improvement affects this initialization.
It's not done for all targets though, as not all targets have linker support
for the init_priority attribute (notably, darwi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364
Tobias Burnus changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112405
Bug ID: 112405
Summary: GCN: "gcc.dg/vect/vect-simd-clone-20.c:22:1: error:
conversion of register to a different size in
'view_convert_expr'"
Product: gcc
Versi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112404
Tamar Christina changed:
What|Removed |Added
Last reconfirmed||2023-11-6
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112404
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112406
Bug ID: 112406
Summary: [14 Regression] Several SPECCPU 2017 benchmarks fail
with internal compiler error: in expand_insn, at
optabs.cc:8305
Product: gcc
Version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111760
--- Comment #8 from CVS Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:0c42741ad95af3a1e3ac07350da4c3a94865ed63
commit r14-5151-g0c42741ad95af3a1e3ac07350da4c3a94865ed63
Author: Robin Dapp
Date: Wed Oct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112350
--- Comment #2 from Mohamed ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112350&GoAheadAndLogIn=1
it's shown here that the warning is triggered by setting -O3 optimization level
to 3.
I don't know if such behavior is expected i.e. triggeri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112404
--- Comment #3 from Richard Biener ---
Two issues, a simple omission where the ICE occurs and then failure to compute
alignment info for SLP of .MASK_LOAD because SLP_INSTANCE_LOADS doesn't
contain them. Oops.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112359
--- Comment #2 from Robin Dapp ---
Would something like
+ bool allow_cond_op = flag_tree_loop_vectorize
+&& !gimple_bb (phi)->loop_father->dont_vectorize;
in convert_scalar_cond_reduction be sufficient or are the more conditions to
check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
Alexandre Oliva changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112359
--- Comment #3 from rguenther at suse dot de ---
On Mon, 6 Nov 2023, rdapp at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112359
>
> --- Comment #2 from Robin Dapp ---
> Would something like
>
> + bool allow_cond_o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #12 from Jonathan Wakely ---
I don't think _M_offset can ever be out of range, it's always set by the
library code.
Doesn't the warning come from this line, which doesn't use _M_offset anyway?
_Bit_type* __q = std::copy(__f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110859
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
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=112404
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
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=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=110641
Jan Hubicka changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from Jan Hubicka
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=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
--- 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=112405
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
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=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=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=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=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=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=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=112408
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |14.0
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
--- 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=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=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
--- 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
--- 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=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
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRME
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=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
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
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=112410
Marek Polacek changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
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=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
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
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=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=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 #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=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=65833
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc d
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=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
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=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=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=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
--- 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=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=112414
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
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=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=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 #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=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=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=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=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=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
--- 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
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|---
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=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=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
1 - 100 of 136 matches
Mail list logo
