Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Host: aarch64-linux
Target: aarch64-linux
Our Aarch64
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Host: aarch64-linux
Target: aarch64-linux
Our Aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113197
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
||jamborm at gcc dot gnu.org
--- Comment #3 from Martin Jambor ---
The testcase has been fixed with r14-4141-gbf6b107e2a3423 (New early
__builtin_unreachable processing.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111291
Martin Jambor changed:
What|Removed |Added
CC|mjambor at suse dot cz |mikael at gcc dot
gnu.org
--- C
||jamborm at gcc dot gnu.org
Status|NEW |RESOLVED
Keywords|needs-bisection |
--- Comment #3 from Martin Jambor ---
This has been fixed with Richi's r14-3982-g9ea74d235c7e78 ( better DCE after
forwprop). Given the tit
||jamborm at gcc dot gnu.org
--- Comment #4 from Martin Jambor ---
This has been fixed with r14-4786-gd118738e71cf46 (Richi's restrict invariant
motion of shifts).
||jamborm at gcc dot gnu.org
--- Comment #5 from Martin Jambor ---
This has been fixed with r14-5109-ga291237b628f41 (Andrew MacLeod: Remove
simple ranges from trailing zero bitmasks.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110941
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110842
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #5 from Martin Jambor ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110768
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110705
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
||jamborm at gcc dot gnu.org
--- Comment #3 from Martin Jambor ---
This has been fixed with r14-4141-gbf6b107e2a3423 (Andrew MacLeod: New early
__builtin_unreachable processing).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110294
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110091
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110065
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110001
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109918
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109828
Martin Jambor changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org
Keyw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109823
Martin Jambor changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
Keyw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #26 from Martin Jambor --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109753
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #11 from Martin Jambor --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109744
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #3 from Martin Jambor ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107823
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #6 from Martin Jambor ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113178
Martin Jambor changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #6 from Martin Jambor ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 113296, which changed state.
Bug 113296 Summary: [14 Regression] SPEC 2006 434.zeusmp segfaults on Aarch64
when built with -Ofast -march=native -flto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113296
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113296
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108007
--- Comment #20 from Martin Jambor ---
I have submitted a slightly modified patch to the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6cyu1e9kw.fsf@/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112616
--- Comment #6 from Martin Jambor ---
(In reply to Andrew Pinski from comment #1)
> # q_11 = PHI <0B(2), removed_return.14_14(D)(4),
> removed_return.14_14(D)(3)>
> _12 = *q_11;
>
>
> WTF
Well, _12 is not used anywhere, so the code ex
at gcc dot gnu.org |jamborm at gcc dot
gnu.org
--- Comment #3 from Martin Jambor ---
Mine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89863
Bug 89863 depends on bug 94629, which changed state.
Bug 94629 Summary: 10 issues located by the PVS-studio static analyzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110422
--- Comment #5 from Martin Jambor ---
Fixed on trunk, I plan to backport to open release branches in the upcoming
weeks.
at gcc dot gnu.org |jamborm at gcc dot
gnu.org
--- Comment #3 from Martin Jambor ---
Still, let me have a look.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629
--- Comment #28 from Martin Jambor ---
(In reply to David Binderman from comment #27)
> The original article checked gcc-10.
> gcc-13 is checked in the following article:
>
> https://pvs-studio.com/en/blog/posts/cpp/1067/
>
> I suspect it would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113490
--- Comment #5 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6cytv3eyy.fsf@/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476
--- Comment #4 from Martin Jambor ---
The right place where to free stuff in lattices post-IPA would be in
ipa_node_params::~ipa_node_params() where we should iterate over lattices and
deinitialize them or perhaps destruct the array because sinc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113490
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108007
--- Comment #22 from Martin Jambor ---
Fixed on trunk. I did not want to backport this but because of PR 112616 I
will probably do after a few weeks on master, if there are no issues.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112616
--- Comment #8 from Martin Jambor ---
Fixed on trunk. I did not want to backport this but because this variant does
not require disabling DCE, I will probably do after a few weeks on master, if
there are no issues.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105275
--- Comment #3 from Martin Jambor ---
I have re-checked this year again (using master revision
r14-7200-g95440171d0e615) but this time on a high-frequency Zen3 CPU (EPYC
75F3). Run-time of 525.x264_r built with master with PGO and -O2 improved
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: liuhongt at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Host: x86_64-linux-gnu
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107946
Martin Jambor changed:
What|Removed |Added
Last reconfirmed||2024-01-26
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113600
--- Comment #4 from Martin Jambor ---
(In reply to Hongtao Liu from comment #2)
> A patch is posted at
> https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640276.html
>
> Would you give a try to see if it fixes the regression, I don't cur
sion: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Host: x86_64-linux
: normal
Priority: P3
Component: gcov-profile
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Host: x86_64-linux, aarch64
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: syq at gcc dot gnu.org
Target Milestone: ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113646
--- Comment #3 from Martin Jambor ---
(In reply to Richard Biener from comment #1)
> Did you try with -fprofile-partial-training (is that default on? it
> probably should ...). Can you please try training with the rate data
> instead of train
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113757
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=113359
--- Comment #9 from Martin Jambor ---
SRA creates the replacements (in GCC 13) during total scalarization,
i.e. the bit that is not driven by pre-existing accesses to
aggregates, but because it sees an aggregate that is small and regular
and so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113359
--- Comment #14 from Martin Jambor ---
(In reply to rguent...@suse.de from comment #13)
> Might be also an interaction with IPA ICF in case there's a pointer to
> the pair involved?
Yes, this is exactly what seems to be happening. The problem
: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Blocks: 26163
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: crazylht at gmail dot com
Blocks: 26163
Target Milestone: ---
Benchmark 416.gamess from SPECINT 2006 recently regressed on
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: hongyuw at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
The run-time of benchmark
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113646
Martin Jambor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: linkw at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux-gnu
Target: sparc-wrs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 109130, which changed state.
Bug 109130 Summary: [13/14/15 Regression] 464.h264ref regressed by 6.5% on a
Neoverse-N1 CPU with PGO, LTO, -Ofast and -march=native
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109130
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109130
Martin Jambor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: law at gcc dot gnu.org
Blocks: 63426
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108007
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
--- Comment #11 from Martin Jambor ---
Our weekend ubsan bootstrap and test (of revision
r15-2173-ge0d997e913f811) still reported failures when compiling
testcase gfortran.dg/ieee/large_1.f90 (at -O2 and higher).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58416
--- Comment #15 from Martin Jambor ---
Created attachment 58724
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58724&action=edit
simple (wip) fix
I'm wondering whether just simply something like this would not be enough. I
have looked at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58416
--- Comment #19 from Martin Jambor ---
(In reply to Richard Biener from comment #18)
> (In reply to Martin Jambor from comment #15)
> > Created attachment 58724 [details]
> > simple (wip) fix
> >
> > I'm wondering whether just simply something l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58416
Martin Jambor changed:
What|Removed |Added
Attachment #58724|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115815
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=114985
--- Comment #35 from Martin Jambor ---
(In reply to Richard Biener from comment #34)
> This is fixed, right?
Well, yes, but as part of this I promised to go over all VR bits in ipa-cp.*
and ipa-prop.* which is still only half done. But I do ha
: UNCONFIRMED
Severity: normal
Priority: P3
Component: gcov-profile
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117211
Martin Jambor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117142
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=115815
--- Comment #9 from Martin Jambor ---
Right, sorry, life intervened. But I am aware of the need to backport.
However, there is a problem with the testcase that should be addressed first:
https://inbox.sourceware.org/gcc-patches/ri6v7xud7pu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115815
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: dmalcolm at gcc dot gnu.org
Target Milestone
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: dmalcolm at gcc dot gnu.org
Blocks: 86656
Target Milestone: ---
Host: x86_64-linux-gnu
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117360
--- Comment #4 from Martin Jambor ---
(In reply to Jeffrey A. Law from comment #3)
> What's interesting is I did a bootstrap with ubsan a while back to chase
> down this stuff. Could be something recently introduced or a path we didn't
> trigge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117442
--- Comment #4 from Martin Jambor ---
(In reply to David Malcolm from comment #3)
> Sorry about the regression. Should be fixed by the above patch.
No worries, thanks for a quick fix!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117764
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117142
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117360
--- Comment #8 from Martin Jambor ---
I can confirm that our UBSAN bootstrap+testsuite buildbot run passed all tests
and is nicely green again. Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118059
--- Comment #5 from Martin Jambor ---
Indeed, our UBSAN testsuite results are green again, thanks for the fix!
: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: jamborm at gcc dot gnu.org
Target Milestone: ---
As discovered in PR 118125 (where the issue was with lto "front-end"),
builtins only get their att
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
at gcc dot gnu.org |jamborm at gcc dot
gnu.org
sion: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: burnus at gcc dot gnu.org
Blocks: 63426
Target
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=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=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
--- 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=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=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=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=117892
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
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=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
at gcc dot gnu.org |jamborm at gcc dot
gnu.org
|1
Status|UNCONFIRMED |NEW
CC||jamborm at gcc dot gnu.org,
||pault at gcc dot gnu.org
--- Comment #1 from Martin Jambor ---
This has started with revision
: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
Target Milestone: ---
In r15-6296-g5d740f56a16270 (Martin Jambor: ipa: Improve how we derive
value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110378
--- Comment #11 from Martin Jambor ---
IIUC only the simplest testcase of the three was fixed. I'll try to re-check
soon-ish.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118138
--- Comment #3 from Martin Jambor ---
I'll have a look, though I may not be able to do so in December.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118097
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118138
Martin Jambor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
2201 - 2300 of 2367 matches
Mail list logo
