https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
Bug ID: 112825
Summary: Modula 2 builds target objects as part of all-gcc
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112278
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112891
--- Comment #4 from Richard Sandiford ---
(In reply to Hongtao Liu from comment #2)
> So it looks like we need to handle ix86_avx_u128_mode_after
>
> --- a/gcc/config/i386/i386.cc
> +++ b/gcc/config/i386/i386.cc
> @@ -15177,7 +15177,14 @@ ix86
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109078
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106694
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101926
Bug 101926 depends on bug 109391, which changed state.
Bug 109391 Summary: Inefficient codegen on AArch64 when structure types are
returned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109391
What|Removed |Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109391
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112933
Richard Sandiford changed:
What|Removed |Added
Last reconfirmed||2023-12-09
Assignee|unass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112931
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112930
Richard Sandiford changed:
What|Removed |Added
Last reconfirmed||2023-12-09
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112930
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112931
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112933
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112948
Richard Sandiford changed:
What|Removed |Added
Last reconfirmed||2023-12-11
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109855
--- Comment #3 from rsandifo at gcc dot gnu.org
---
Looking at the mddump file, the output predicate and constraint
seem to have gone AWOL:
;; /home/ricsan01/gnu/src/gcc/gcc/config/aarch64/aarch64-simd.md: 1554
(define_insn ("aarch64_mlav4hi_v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109855
--- Comment #4 from rsandifo at gcc dot gnu.org
---
I guess the problem is that the define_subst output template has:
(match_operand: 0)
which creates a new operand 0 with an empty predicate and constraint,
as opposed to a (match_dup 0), wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109940
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109632
--- Comment #12 from rsandifo at gcc dot gnu.org
---
The patch in comment 11 is just a related spot improvement.
The PR itself is still unfixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109940
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resoluti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109964
--- Comment #4 from rsandifo at gcc dot gnu.org
---
(In reply to Richard Biener from comment #3)
> So the bug in the vectorizer is that it does
>
> t.ii:14:5: note: can narrow to signed:16 without loss of precision: _31 =
> 1 >> _30;
> t.ii:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110039
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110105
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110248
--- Comment #5 from rsandifo at gcc dot gnu.org
---
ivopts does have code to treat ifn pointer arguments specially,
see get_mem_type_for_internal_fn &co. But like Kewen says,
it's still only based on the mode.
Personally I'd prefer an interna
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70150
--- Comment #32 from rsandifo at gcc dot gnu.org
---
(In reply to Xi Ruoyao from comment #31)
> Richard: is it allowed to backport them (or the entire
> https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613093.html series) for
> gcc-12?
Yeah,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106081
--- Comment #7 from rsandifo at gcc dot gnu.org
---
I don't think the splat creates a new layout, but instead a
splat should be allowed to change its layout at zero cost.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110449
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110485
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||avieira at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495
--- Comment #2 from rsandifo at gcc dot gnu.org
---
The point of the builder is that, if you know the pattern,
you don't need to supply every element value to the builder.
(And indeed you can't when the vector is variable length.)
So something
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110625
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110625
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assign
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110625
--- Comment #7 from rsandifo at gcc dot gnu.org
---
The current issue rate framework was originally written for Neoverse V1 and
Neoverse V2. For those cores, it wasn't necessary to make a distinction
between scalar integer operations and scala
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80283
--- Comment #39 from Richard Sandiford ---
(In reply to Andrew Pinski from comment #38)
> For aarch64, the test from comment #11 is so much worse on the trunk than in
> GCC 13.2.0.
I've been working on a fix for that. I'm hoping to post it today
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109543
--- Comment #5 from Richard Sandiford ---
I think the loop in compute_mode_layout needs to be smarter
for unions. At the moment it's sensitive to field order,
which doesn't make much conceptual sense.
E.g. for the admittedly contrived example:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113027
Bug ID: 113027
Summary: aarch64 is missing vec_set and vec_extract for
structure modes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111702
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113094
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112948
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113094
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113091
--- Comment #5 from Richard Sandiford ---
> The issue here is that because the "outer" pattern consumes
> patt_64 = (int) patt_63 it should have adjusted _2 = (int) _1
> stmt-to-vectorize
> as being the outer pattern root stmt for all this logi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113104
Richard Sandiford changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113196
Bug ID: 113196
Summary: [14 Regression] Failure to use ushll{,2}
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113196
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113220
Richard Sandiford changed:
What|Removed |Added
CC|richard.sandiford at arm dot com |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68703
Richard Sandiford changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113104
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113270
--- Comment #6 from Richard Sandiford ---
I think we want the patch in comment 3, but in addition, I then also needed to
use the following for a similar SVE case:
extern GTY(()) tree scalar_types[NUM_VECTOR_TYPES + 1];
tree scalar_types[NUM_VEC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113270
--- Comment #8 from Richard Sandiford ---
Thanks for trying it, and sorry for not doing it myself.
The patch LGTM FWIW, so preapproved if it passes testing (which I'm sure it
will :))
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112989
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112989
--- Comment #12 from Richard Sandiford ---
> another is try
> #pragma GCC aarch64 "arm_sve.h"
> after a couple of intentional declarations of the SVE builtins with
> non-standard return/argument types and make sure that while it emits some
> err
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112989
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113196
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111267
--- Comment #12 from Richard Sandiford ---
I don't object to the patch, but for the record: the current heuristics go back
a long way. Although I reworked the pass to use rtl-ssa a few years ago, I
tried as far as possible to preserve the old h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109929
--- Comment #7 from Richard Sandiford ---
Hmm, yeah, like you say, neither of those commits should have made a different
to whether bootstrap works. I guess the problem is just latent now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113485
Richard Sandiford changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #7 from Richar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113572
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113281
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #13 from Richard Sandiford ---
I don't think there's any principle that upper bits must be zero.
How do we end up with a pattern that depends on that being the case?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113572
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113485
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113550
Richard Sandiford changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #16 from Richard Sandiford ---
(In reply to Richard Biener from comment #15)
> I think the problem is the cbranch pattern which looks at all of the
> QImode mask - but of course it doesn't know it's really V4BImode it's
> working on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #18 from Richard Sandiford ---
(In reply to Tamar Christina from comment #17)
> Well the mid-end has generated the right precision. The type it generates is
> vector(4) vexit_reduc_67;
> so it does say it's a single bit boolean.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113613
Richard Sandiford changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113281
--- Comment #24 from Richard Sandiford ---
Fixed on trunk so far, but it's latent on branches. I'll see what
the trunk fallout is like before asking about backports.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113636
Richard Sandiford changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113623
Richard Sandiford changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677
--- Comment #21 from Richard Sandiford ---
(In reply to Alex Coplan from comment #13)
> The problem seems to be this code in aarch64_process_components:
>
> while (regno != last_regno)
> {
> bool frame_related_p = aarch64_emit_cfi_f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113623
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113636
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #30 from Richard Sandiford ---
(In reply to Richard Biener from comment #29)
> But that's just for CONSTRUCTORs, we got the VIEW_CONVERT_EXPR path for
> VECTOR_CSTs. But yeah, that _might_ argue we should perform the same
> masking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #34 from Richard Sandiford ---
(In reply to Richard Biener from comment #32)
> Btw, AVX512 knotb will invert all 8 bits and there's no knot just affecting
> the lowest 4 or 2 bits.
>
> It all feels like desaster waiting to happen ;)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113763
--- Comment #11 from Richard Sandiford ---
Currently away so can't try it myself, but how about just using an ad-hoc
structure instead?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113763
--- Comment #14 from Richard Sandiford ---
AFAIK, the constructor shouldn't be necessary. (And without it, the whole
thing would fit on one line.) LGTM (and preapproved) otherwise. Thanks for
doing this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115281
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115464
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115464
Richard Sandiford changed:
What|Removed |Added
Known to work||15.0
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115464
--- Comment #11 from Richard Sandiford ---
Yeah, like I mentioned in the commit message, I'm in the process of rolling
this fix out to more places. Was just testing the waters with the minimal fix
for comment 4.
But yeah, maybe more of it will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115518
Bug ID: 115518
Summary: aarch64: Poor codegen for arm_neon_sve_bridge.h
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: aarch64-sve
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114996
Richard Sandiford changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594
Richard Sandiford changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114515
Richard Sandiford changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115610
Bug ID: 115610
Summary: -flate-combine disabled by default for x86 port
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancemen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115612
Bug ID: 115612
Summary: powerpc: define_insn_and_splits calling gen_reg_rtx
unconditionally
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-val
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115613
Bug ID: 115613
Summary: xtensa: splits dependent on can_create_pseudo_p
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115478
Richard Sandiford changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115622
--- Comment #1 from Richard Sandiford ---
Are you sure about the bisection? late-combine only affects RTL, and in any
case is disabled by default for powerpc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115631
--- Comment #2 from Richard Sandiford ---
I suppose for issues like this, it would be useful to have a debug counter to
bisect on. I'll post a patch for doing that today, but I'm afraid I'll be
relying on someone with gcn access to actually do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115633
--- Comment #2 from Richard Sandiford ---
-flate-combine-instructions is supposed to be disabled by default for all
powerpc targets. Could you look at why that isn't the case for you?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115631
--- Comment #3 from Richard Sandiford ---
I've now pushed a debug counter for late_combine. Sorry to ask, but could you
bisect on N in -fdbg-cnt=late_combine:N to see which transformation is causing
the problem?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115631
--- Comment #4 from Richard Sandiford ---
Created attachment 58513
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58513&action=edit
A patch for a bug seen on arm*-*-*
Also, could you check whether the attached patch makes any difference?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114531
--- Comment #17 from Richard Sandiford ---
I can see that it's useful to ask whether the current -O2 & -O3 inlining
heuristics are making the right trade-off. But I think that's really a
different issue from the one that is raised in the PR. (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115634
--- Comment #3 from Richard Sandiford ---
Yeah, I agree that sounds like the right fix. Specifically, I assume
s390_decompose_addrstyle_without_index, when doing:
if (op && GET_CODE (op) != REG)
return false;
should check whether the re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115677
Richard Sandiford changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115677
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115629
Richard Sandiford changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115782
Richard Sandiford changed:
What|Removed |Added
Last reconfirmed||2024-07-05
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115785
Richard Sandiford changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114531
--- Comment #20 from Richard Sandiford ---
(In reply to Jan Hubicka from comment #18)
> I am trying to understand how useful this is. I am basically worried
> about two things
> 1) we have other optimization passes that behave differently at -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115785
--- Comment #2 from Richard Sandiford ---
The patch in #c1 is just part 1. Part 2 will fix the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115782
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
601 - 700 of 894 matches
Mail list logo