https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119085
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117423
--- Comment #23 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6ms92blnz@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117423
Martin Jambor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121023
Martin Jambor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120987
--- Comment #9 from Martin Jambor ---
(In reply to Andrew Pinski from comment #6)
> I suspect this just exposes the latent issue. This pushes for more SRA on
> some arguments.
Specifically those where ipa-modref says it is safe - that can be
be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #7 from Martin Jambor ---
(In reply to kargls from comment #5)
>
> So, if I understand, you want an fnspec of ". . w w w w w w w".
> Can you show f->sym and f->sym-attr from gdb?
>
(gdb) p *f->sym
$5 = {name = 0x7fffbe64a100 "_for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120960
Bug ID: 120960
Summary: jit: The static initialization of builtin_data uses
flag_openacc and flag_openmp (which have not been set
yet)
Product: gcc
Version: 15.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #3 from Martin Jambor ---
SRA is "Scalar Replacement of Aggregates" pass. It is one of our
optimization passes which can split up aggregates into scalar
components and thus allow further optimizations.
To "escape" means that the ad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #1 from Martin Jambor ---
And indeed the following hack in Fortran FE "fixes" the benchmark (of
course, this is not meant as a proposed fix, just as a demonstration
where the problem is):
diff --git a/gcc/fortran/trans-types.cc b/gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
Bug ID: 120958
Summary: tree-sra "miscompiles" asynchronous MPI (mpi_irecv) in
Fortran 77 because of wrong fnspec
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120295
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120622
--- Comment #7 from Martin Jambor ---
Thank you very much for your analysis. The commit you referenced indeed does
not help.
I have filed a new upstream issue:
https://github.com/serge-sans-paille/pythran/issues/2324
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114864
Bug 114864 depends on bug 111873, which changed state.
Bug 111873 Summary: [12/13/14/15 regression] runtime Segmentation fault with
'-O3 -fno-code-hoisting -fno-early-inlining -fno-tree-fre -fno-tree-pre' since
r12-434-g93f8cb4965cebe
https://g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120622
--- Comment #2 from Martin Jambor ---
Created attachment 61613
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61613&action=edit
Reduced test-case
This is a reduced self-contained (other than the libstdc++ dependency)
test-case that I obta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120622
--- Comment #1 from Martin Jambor ---
Created attachment 61612
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61612&action=edit
Unreduced test-case
This is a tarball with the original code snipped from pythran, the
"pythonic" "library" it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120622
Bug ID: 120622
Summary: Compilation error ( no match for operator==) since
libstdc++ commit r15-4475-g7ed561f63e7955
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119930
--- Comment #11 from Martin Jambor ---
(In reply to Sam James from comment #4)
> -fno-ipa-cp works
It does not help for me, can you double check, please?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120295
--- Comment #10 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6h61fwbp5@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282
Martin Jambor changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99912
Martin Jambor changed:
What|Removed |Added
CC||19373742 at buaa dot edu.cn
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282
--- Comment #20 from Martin Jambor ---
(In reply to mcccs from comment #17)
>
[...]
>
> The problem is that the parameter pointer is not set to the argument so
> dereferencing it causes a segfault. Dumping all the passes, this problem is
> firs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120295
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93271
--- Comment #22 from Martin Jambor ---
(In reply to Jakub Jelinek from comment #21)
> Martin, could we backport r15-3070 to 14.3?
It depends on r15-2476-gb3974356b0981c which, IIRC, Richi was not planning to
backport.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
--- Comment #17 from Martin Jambor ---
*** Bug 120044 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120044
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
--- Comment #16 from Martin Jambor ---
I have proposed a patch on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6h61oyzn1@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119852
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120044
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120048
--- Comment #10 from Martin Jambor ---
The workaround looks reasonable to me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118924
Martin Jambor changed:
What|Removed |Added
Summary|[12/13/14 regression] Wrong |[12 regression] Wrong code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119852
Martin Jambor changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119852
Bug ID: 119852
Summary: The output of -fdump-ipa-clones can contain "(null)"
as the suffix/reason for cloning
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119614
Martin Jambor changed:
What|Removed |Added
Assignee|jamborm at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119803
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119614
--- Comment #33 from Martin Jambor ---
The patch from comment #32 passes LTO-bootstrap and profiled-LTO-bootstrap on
x86_64-linux. I have asked Honza to look at it and comment, especially on the
decision to put the return VR into clone_info des
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119803
--- Comment #9 from Martin Jambor ---
I have posted a patch with the change proposed by Jakub to the mailing list:
https://inbox.sourceware.org/gcc-patches/ri67c3lbm7q@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119614
--- Comment #32 from Martin Jambor ---
Created attachment 61119
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61119&action=edit
Fixed WIP patch
Right, I forgot to modify output_cgraph_opt_summary_p as well, which was not
necessary for th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119803
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119614
--- Comment #27 from Martin Jambor ---
Created attachment 61116
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61116&action=edit
WIP and only mildly tested patch
This is my current WIP patch, so far only mildly tested, but which
fixes the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119318
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119298
Martin Jambor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118924
Martin Jambor changed:
What|Removed |Added
Summary|[12/13/14/15 regression]|[12/13/14 regression] Wrong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119614
Martin Jambor changed:
What|Removed |Added
Assignee|jakub at gcc dot gnu.org |jamborm at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119318
--- Comment #8 from Martin Jambor ---
(In reply to Sam James from comment #6)
> Maybe add the PR119530 testcase as well? It is structurally similar, but it
> lacks vectors so may be more useful food for the fuzzers.
I have that on my TODO list,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119318
--- Comment #7 from Martin Jambor ---
...and that one consists of the first and second patch in the series at
https://inbox.sourceware.org/gcc-patches/cover.1743458148.git.jamb...@gcc.gnu.org/T/#t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116572
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119530
Martin Jambor changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119318
--- Comment #5 from Martin Jambor ---
Created attachment 60939
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60939&action=edit
Simple fix
This patch is a simple fix. I'll submit one streaming the necessary type to
the mailing list thoug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119318
Martin Jambor changed:
What|Removed |Added
CC||zhendong.su at inf dot ethz.ch
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118924
--- Comment #18 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6ldslmk3y@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119493
--- Comment #15 from Martin Jambor ---
(In reply to Jakub Jelinek from comment #12)
> For musttail, perhaps SRA could avoid changing the path from musttail call
> return to the return stmt.
> I've tried
> --- gcc/tree-sra.cc.jj2025-01-02
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119318
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119298
--- Comment #3 from Martin Jambor ---
Created attachment 60759
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60759&action=edit
Output of -fopt-info-vec in the slow case
Output of -fopt-info-vec in the slow case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119298
Bug ID: 119298
Summary: 538.imagick_r is faster when compiled with GCC 14.2
and -Ofast -flto -march=native than with master on
Zen5
Product: gcc
Version: 15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119298
--- Comment #4 from Martin Jambor ---
Created attachment 60760
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60760&action=edit
Output of -fopt-info-vec in the fast case
Output of -fopt-info-vec in the fast case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119298
--- Comment #1 from Martin Jambor ---
Created attachment 60757
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60757&action=edit
Perf annotate of the slow case
Perf annotate of the slow case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119298
--- Comment #2 from Martin Jambor ---
Created attachment 60758
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60758&action=edit
Perf annotate of the fast case
Perf annotate of the fast case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116572
Martin Jambor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118243
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118924
--- Comment #17 from Martin Jambor ---
After reading from ao_compare::compare_ao_refs, I tend to think the
correct predicate for "tbaa_hazard" from my comment #14 is
types_equal_for_same_type_for_tbaa_p (with the last argument true in
early SRA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118318
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45375
Bug 45375 depends on bug 118318, which changed state.
Bug 118318 Summary: [15 regression] ICE when building firefox-134.0 with PGO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118318
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118924
--- Comment #14 from Martin Jambor ---
So something like the following - which is completely untested, the
type test may be a wrong one, I'd like to think this through a little
more before actually proposing this, but any comments still welcome:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118924
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118785
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118318
--- Comment #18 from Martin Jambor ---
I have proposed the patch on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6bjui45il@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118318
Martin Jambor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119069
Bug ID: 119069
Summary: 519.lbm_r runs 60% slower with -Ofast -flto
-march=znver5 on an AMD Zen5 machine than when
compiled with GCC 14 (or with -march=znver4)
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118318
--- Comment #16 from Martin Jambor ---
(In reply to Jan Hubicka from comment #13)
>
[...]
>
> Here are two calls to + and it is not clear which one triggers the ICE.
> However sum += e->count.ipa (); quite obviously preserves the fact that sum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118785
--- Comment #12 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6tt8i58kq@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86270
--- Comment #20 from Martin Jambor ---
We no longer track Zen1 performence, but this hasbrought about a dramatic
improvement of 465.tonto on our SomeKindOfLake machine:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=464.230.0
Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 118125, which changed state.
Bug 118125 Summary: [15 Regression] 7-16% slowdown of 510.parest_r on
x86-64(-v3) since r15-6110-g92e0e0f8177530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
What|Remove
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118858
Bug 118858 depends on bug 118125, which changed state.
Bug 118125 Summary: [15 Regression] 7-16% slowdown of 510.parest_r on
x86-64(-v3) since r15-6110-g92e0e0f8177530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
What|Remo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118862
Bug ID: 118862
Summary: UBSAN: shift exponent too large since
r15-7345-gc2a0ee58865c5a
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118858
--- Comment #3 from Martin Jambor ---
The reason why I only added cold was not a question of streaming (I don't think
we avoid any this way) but rather me being lazy, in the sense that I really
wanted the cold attribute to go in reasonably quick
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118097
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118852
Bug ID: 118852
Summary: Train run of 502.gcc_r compiled with -Ofast
-fprofile-generate -march=x86_64-v3 fails
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118785
Martin Jambor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
--- Comment #14 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6a5atcvem@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118243
--- Comment #12 from Martin Jambor ---
I have proposed a patch on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6cyfpcviz@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118243
--- Comment #11 from Martin Jambor ---
(In reply to Richard Biener from comment #9)
> Indeed we don't seem to split a vector in the same way:
>
We do but the constant IPA-CP is different, is it is the entire vector in one
constant, as opposed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118785
--- Comment #10 from Martin Jambor ---
Could be, I am about to re-test and commit a patch for PR 118097 which was
approved on Friday and which addresses use of wrong types for IPA-CP
calculation (the patch alone does not fix this ICE, though).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118243
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118243
--- Comment #10 from Martin Jambor ---
This is an equivalent testcase without OpenMP and especially without iostream,
making dump reading a bit easier:
using complex_t = double __complex__;
struct A {
complex_t value;
A(double r) : valu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118746
Bug ID: 118746
Summary: In go FE, __builtin_unreachable does not have the
attribute cold - or any attribute, for that matter
Product: gcc
Version: 15.0
Status: UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118745
Bug ID: 118745
Summary: UBSAN: member access within null pointer of type
'struct gfc_omp_namelist' since
r15-7285-gbea86e82146b9b
Product: gcc
Version: 15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
--- Comment #12 from Martin Jambor ---
The cold attribute is simply and silently dropped on the floor by
decl_attributes (in attribs.cc) in the process of building decls for
builtins because it cannot look it up in the gnu attribute name space
b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
--- Comment #10 from Martin Jambor ---
For some reason, unlikely_executed_stmt_p (and thus
unlikely_executed_bb_p) do not see that __builtin_unreachable is a
cold function:
(gdb) pt decl
>
QI
size
unit-size
al
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
--- Comment #11 from Martin Jambor ---
The issue can also be reproduced with applying:
diff --git a/gcc/ipa-fnsummary.cc b/gcc/ipa-fnsummary.cc
index 33f19365ec3..4c062fe8a0e 100644
--- a/gcc/ipa-fnsummary.cc
+++ b/gcc/ipa-fnsummary.cc
@@ -255,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118683
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 118683, which changed state.
Bug 118683 Summary: UBSAN: Invalid value for type ar_type since
r15-7070-g0d1e62b83561ba
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118683
What|Removed |A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
--- Comment #9 from Martin Jambor ---
Passing -fdisable-tree-rebuild_frequencies1 to the LTO linking step
brings back the original performance.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
--- Comment #8 from Martin Jambor ---
I guess I should have started with looking at annotated assembly. The
hot loop in the hot functions changes from:
53 : ,-> 5534e0: lea(%r11,%rax,1),%rsi
659 : | 5534e4: mov(%rsi),%edi
48
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117892
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118125
--- Comment #7 from Martin Jambor ---
(In reply to Martin Jambor from comment #4)
> [...] Unfortunately when I
> then looked at SLP vectorization when all IPA-VR propagations were
> allowed again, this particular case was not there (but there we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118683
Bug ID: 118683
Summary: UBSAN: Invalid value for type ar_type since
r15-7070-g0d1e62b83561ba
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117892
--- Comment #8 from Martin Jambor ---
I have proposed a patch to address this on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6zfjce03l@virgil.suse.cz/T/#u
1 - 100 of 716 matches
Mail list logo