https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
--- Comment #6 from Richard Biener ---
So the main issue is that we are not updating the store motion pass meta-data
after applying store-motion to an outer loop and then continue to analyze
inner loops. In particular the somewhat recent additi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
--- Comment #5 from Andrew Pinski ---
(In reply to David Binderman from comment #4)
> Created attachment 58755 [details]
> C source code
>
> Original code. Produced by csmith.
Note it looks like the original code didn't have the uninitialized
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116074
Tamar Christina changed:
What|Removed |Added
Last reconfirmed||2024-07-25
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116085
--- Comment #1 from Patrick O'Neill ---
Tested using r15-2276-gd2fc64c8578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
--- Comment #4 from David Binderman ---
Created attachment 58755
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58755&action=edit
C source code
Original code. Produced by csmith.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116085
Bug ID: 116085
Summary: RISC-V: Miscompile at -O2 with zbb
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116081
--- Comment #4 from Andrew Pinski ---
Maybe it is operand_equal_p that is the issue here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116084
Bug ID: 116084
Summary: Use dot-product instructions for byte->word PLUS
reductions in vectorisation
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116081
--- Comment #3 from Richard Biener ---
Yeah, that doesn't fix the SHL_INSERT.
@@ -3628,17 +3628,17 @@
t.c:14:21: note: -->vectorizing phi: i_12 = PHI
t.c:14:21: note: -->vectorizing phi: ivtmp_14 = PHI
t.c:14:21: note: -->ve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116081
--- Comment #2 from Richard Biener ---
diff --git a/gcc/tree-vect-stmts.cc b/gcc/tree-vect-stmts.cc
index a47482375c1..aa98599c1f5 100644
--- a/gcc/tree-vect-stmts.cc
+++ b/gcc/tree-vect-stmts.cc
@@ -14905,7 +14905,7 @@ vect_get_vector_types_for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116081
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116080
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Component|other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116075
--- Comment #4 from Richard Biener ---
fold_const_all misses VEC_SHL_INSERT folding (and probably many(?) others)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116065
--- Comment #3 from Haochen Jiang ---
Maybe I could first start with a bisect since GCC12.1 is known to ok and
GCC13.1 is known to fail.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116074
Richard Biener changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116080
--- Comment #4 from Haochen Jiang ---
Hmm, it is interesting that I even could not reproduce that on the same
machine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87985
--- Comment #9 from Richard Biener ---
(In reply to Richard Biener from comment #8)
> Confirmed.
>
> tree slp vectorization : 67.60 ( 85%)
>
> I don't have an unpatched tree around but the issue doesn't seem to be the
> same
> so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116082
uecker at gcc dot gnu.org changed:
What|Removed |Added
CC||uecker at gcc dot gnu.org
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116083
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116083
Bug ID: 116083
Summary: Re-surfacing SLP vectorization slowness for
gcc.dg/pr87985.c
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87985
--- Comment #8 from Richard Biener ---
Confirmed.
tree slp vectorization : 67.60 ( 85%)
I don't have an unpatched tree around but the issue doesn't seem to be the same
so lets open a new PR for it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116082
Sam James changed:
What|Removed |Added
CC||alx at kernel dot org,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116074
--- Comment #4 from Sam James ---
Created attachment 58754
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58754&action=edit
reduced.ii
Still pretty big.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115185
--- Comment #21 from Andrew Pinski ---
(In reply to Wentao Zhang from comment #18)
> This produces warnings in kernel defconfig builds and they become errors due
> to
> CONFIG_WERROR.
>
> Cases I've observed so far:
>
> 1. initialization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115185
--- Comment #20 from Wentao Zhang ---
(In reply to Wentao Zhang from comment #18)
>
> will get expanded to
>
> [POWER_SUPPLY_PROP_CHARGE_CONTROL_START_THRESHOLD] = {
> .prop_name = "CHARGE_CONTROL_START_THRESHOLD",
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116082
Bug ID: 116082
Summary: -Wunterminated-string-initialization should not warn
about strings that end with "\0" but should warn still
for -Wc++-compat
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115185
--- Comment #19 from Andrew Pinski ---
(In reply to Wentao Zhang from comment #18)
>
> will get expanded to
>
> [POWER_SUPPLY_PROP_CHARGE_CONTROL_START_THRESHOLD] = {
> .prop_name = "CHARGE_CONTROL_START_THRESHOLD",
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116058
--- Comment #11 from Jeffrey A. Law ---
The patch looks to do basically the right thing and given Richard knows his
code better than I, let's go with it.
I'll respin sh4* once it lands upstream to see if there's any change.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115185
Wentao Zhang changed:
What|Removed |Added
CC||wentaoz5 at illinois dot edu
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116075
--- Comment #3 from Andrew Pinski ---
Note I filed PR 116081 for maybe the real issue with the original testcase
where there is a difference if you use a typedef or not. I am going to keep
this for optimizing VEC_SHL_INSERT though because I have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116081
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116081
Bug ID: 116081
Summary: [15 Regression] Different code generation in the
vectorizer with a typedef vs not
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116080
Haochen Jiang changed:
What|Removed |Added
CC||haochen.jiang at intel dot com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115086
--- Comment #14 from Andrew Pinski ---
Patch set submitted:
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/658219.html
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/658218.html
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/65822
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115749
--- Comment #13 from GCC Commits ---
The master branch has been updated by Kong Lingling :
https://gcc.gnu.org/g:bc00de070f0b9a25f68ffddbefe516543a44bd23
commit r15-2295-gbc00de070f0b9a25f68ffddbefe516543a44bd23
Author: Lingling Kong
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115978
--- Comment #10 from Hongtao Liu ---
(In reply to H.J. Lu from comment #9)
> (In reply to Hongtao Liu from comment #8)
> > Fixed in GCC15,thanks H.J.
>
> Does GCC 14 have the same issue with -m32 -march=native?
Yes, will backport the patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116053
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #2 from And
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
Bill Wendling changed:
What|Removed |Added
CC||isanbard at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116053
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-07-25
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105612
Bug 105612 depends on bug 116069, which changed state.
Bug 116069 Summary: tautological-compare warnings observed only with -save-temps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116069
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80369
Andrew Pinski changed:
What|Removed |Added
CC||jbeulich at suse dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116069
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116069
--- Comment #1 from Andrew Pinski ---
This happens IIRC tracking from macros is lost.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116076
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116076
--- Comment #1 from Andrew Pinski ---
Might be:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=1e3aa9c9278db69d4bdb661a750a7268789188d6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107211
--- Comment #7 from Andrew Pinski ---
(In reply to Tymi from comment #6)
> And just as an addition, it always yields true.
> For example here:
> ```cpp
> int awoo(void) noexcept(false);
> int awoo(int) noexcept(false);
>
> int main(void)
> {
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116080
--- Comment #2 from Andi Kleen ---
Also can you upload the whole log files somewhere? I would like to see what the
output of check_effective_target_struct_tail_call is. It should have caught
some of these problems.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-07-24
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Summary|ice during GIMP
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116080
--- Comment #1 from Andi Kleen ---
Yes it is known that powerpc (or some flavors of it) has poor tail call support
due to ABI limitations.
Just need to figure out how to skip the test. I guess it needs a better test in
check_effective_target_ta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116064
--- Comment #6 from Andrew Pinski ---
By the way Xalan even upstream still has this bug.
https://github.com/apache/xalan-c/blob/c326619da4813acfc845c2830d904a4860f9afe1/src/xalanc/XMLSupport/XalanOtherEncodingWriter.hpp#L323
They do have a jira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116080
Bug ID: 116080
Summary: New tests from r15-2233-g8d1af8f904a0c0 fail
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: oth
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
Jonathan Wakely changed:
What|Removed |Added
Summary|[14/15 Regression] broken |[14 Regression] broken
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116075
--- Comment #2 from Andrew Pinski ---
Short not using the vectorizer testcase:
```
#include
svint8_t f(void)
{
svint8_t tt;
tt = svdup_s8 (0);
tt = svinsr (tt, 0);
return tt;
}
```
Note LLVM does not optimize the above to just `mov z3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
--- Comment #2 from Andrew Pinski ---
Also what glibc version is on the system? Since if it is std::find that is
causing the regression memchr was improved in the last year or so in glibc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116071
--- Comment #4 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:8c71830b51e6fd10087ce3f6791de80eb1f10b96
commit r15-2277-g8c71830b51e6fd10087ce3f6791de80eb1f10b96
Author: Jason Merrill
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
David Binderman changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115991
--- Comment #13 from Sergei Trofimovich ---
(In reply to Andrew Pinski from comment #1)
> BUT BUT ivopts does:
>
> _30 = (unsigned int) &hdr;
> ivtmp.22_24 = -_30;
>
> which does not make sense.
>
> So I think this is a bug in IV_OPTs in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116074
--- Comment #3 from Sam James ---
Created attachment 58753
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58753&action=edit
partial.ii.xz
Reduction is slowgoing. Attached a partial one while it carries on. I've not
tried to isolate it man
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116044
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #3
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=116039
--- Comment #2 from Jeffrey A. Law ---
Very interesting little testcase. This may be the loongarch bug that was
recently reported.
It appears the root cause is this insn (from a hacked up version, so the insn
#s may not match up perfectly):
(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90608
--- Comment #22 from Tamar Christina ---
(In reply to Mikael Morin from comment #21)
> (In reply to Tamar Christina from comment #20)
> > Hi Mikael,
> >
> > I did regression testing on x86_64 and AArch64 and only found one test-ism.
> >
> > I t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116079
Bug ID: 116079
Summary: ice during GIMPLE pass lim
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107211
Tymi changed:
What|Removed |Added
CC||wilczew.tymon at gmail dot com
--- Comment #6 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116057
--- Comment #15 from Sasha Finkelstein ---
Created attachment 58751
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58751&action=edit
Full preprocessed source part 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116057
--- Comment #14 from Sasha Finkelstein ---
Created attachment 58750
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58750&action=edit
Full preprocessed source part 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87985
--- Comment #7 from Andrew Pinski ---
This seems to regressed again on the trunk for aarch64 (didn't check x86_64).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116078
Filip Kastl changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116078
Bug ID: 116078
Summary: [15 Regression] 10-12% slowdown of 436.cactusADM on
AMD Zen2
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: needs-bisection
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109126
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94404
Bug 94404 depends on bug 116077, which changed state.
Bug 116077 Summary: GCC hasn't implemented CWG DR 2387
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116077
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109126
Andrew Pinski changed:
What|Removed |Added
CC||de34 at live dot cn
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116077
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116067
--- Comment #4 from Jeffrey A. Law ---
And Sam, yes, absolutely OK to just assign anything that looks ext-dce related
to me. Hoping with today's change things should start settling down and I can
focus on addressing some longer term maintainabi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116037
--- Comment #6 from Jeffrey A. Law ---
*** Bug 116067 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116067
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116077
Bug ID: 116077
Summary: GCC hasn't implemented CWG DR 2387
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116059
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116037
Jeffrey A. Law changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115767
--- Comment #9 from Ignacy Gawędzki ---
(In reply to Sam James from comment #8)
> While we wait for Honza, Ignacy, if you could try reduce it to get rid of
> the Boost dependency, it'd be appreciated.
I'm struggling to get a minimal example. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116037
--- Comment #4 from GCC Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:679086172b84be18c55fdbb9cda7e97806e7c083
commit r15-2275-g679086172b84be18c55fdbb9cda7e97806e7c083
Author: Jeff Law
Date: Wed Jul 24
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116076
Bug ID: 116076
Summary: [15 Regression] slowdown of 433.milc on AMD Zen4
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: needs-bisection
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
Jonathan Wakely changed:
What|Removed |Added
Known to work||13.3.1
Summary|[13/14/15 R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
--- Comment #11 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:46d68bc90688745fc9f25795c371ecaf21e18b56
commit r13-8943-g46d68bc90688745fc9f25795c371ecaf21e18b56
Author: Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116061
--- Comment #7 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:181f40f5cf8510a16191e4768dadbe2cb7a5c095
commit r14-10507-g181f40f5cf8510a16191e4768dadbe2cb7a5c095
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116034
--- Comment #13 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:181f40f5cf8510a16191e4768dadbe2cb7a5c095
commit r14-10507-g181f40f5cf8510a16191e4768dadbe2cb7a5c095
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116061
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:69e69847e21a8d951ab5f09fd3421449564dba31
commit r15-2274-g69e69847e21a8d951ab5f09fd3421449564dba31
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116034
--- Comment #12 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:69e69847e21a8d951ab5f09fd3421449564dba31
commit r15-2274-g69e69847e21a8d951ab5f09fd3421449564dba31
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
--- Comment #10 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:6c22fe418cff57dad712c4b950638e6e2d09bd9c
commit r15-2273-g6c22fe418cff57dad712c4b950638e6e2d09bd9c
Author: Jonathan Wakely
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116070
--- Comment #9 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:5fc9c40fea2481e56bf7bcc994cb40c71e28abb8
commit r15-2272-g5fc9c40fea2481e56bf7bcc994cb40c71e28abb8
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116059
--- Comment #5 from Andrew Pinski ---
(In reply to Robin Dapp from comment #4)
> Strange, Andrew's comment didn't reach my inbox while both of Patrick's did.
Are you subscribed to gcc-bugs@ if not then you were added to the CC after my
comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114665
--- Comment #11 from Patrick O'Neill ---
(In reply to Robin Dapp from comment #10)
> Arg, no, disregard. I was just looking for FFB5 as a failure but I'm
> actually still seeing FFB5 for -O2, -O3, rv64gc etc.
Ah bummer. Hopefully someo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116072
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116035
--- Comment #8 from Patrick O'Neill ---
(In reply to Sam James from comment #7)
> (In reply to Patrick O'Neill from comment #5)
...
> > Typically I use [14/15 Regression] if I'm sure it's a regression (ex. the
> > feature exists in prior version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116035
--- Comment #7 from Sam James ---
(In reply to Patrick O'Neill from comment #5)
> (In reply to Sam James from comment #3)
> > I assume this is a '[14/15 regression]', or does < 14 not support these
> > instructions and you're using it just to sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116035
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116033
--- Comment #2 from Christoph Müllner ---
Jeff Law claimed that th_classify_address() is likely missing a mode check.
I checked that before, and there is a mode check there.
But, after this comment, I challenged the test and indeed:
if (!(INTE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116074
--- Comment #2 from Andrew Pinski ---
opt_machine_mode
related_int_vector_mode (machine_mode vector_mode)
{
gcc_assert (VECTOR_MODE_P (vector_mode));
So it is not passing a vector type here ...
1 - 100 of 223 matches
Mail list logo