https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99656
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Summary|ICE in linear_loa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99657
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99658
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99663
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99660
Richard Biener changed:
What|Removed |Added
Keywords||build
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99668
Bug ID: 99668
Summary: Converting argument _Complex double to double vector
causes STLF stall
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99670
Bug ID: 99670
Summary: IPA CP and SRA pass order issue?
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99656
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99675
Richard Biener changed:
What|Removed |Added
Summary|[11 Regression] ICE during |[10/11 Regression] ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99677
--- Comment #5 from Richard Biener ---
I think Andrew is correct. Note we can't elide "unused" not statically
initialized variables (since the initialization is seen as use).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99693
Richard Biener changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99694
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99696
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99703
--- Comment #3 from Richard Biener ---
Try --disable-cet as a workaround
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99706
--- Comment #4 from Richard Biener ---
Likely an "RTL expansion testcase" using the GIMPLE FE with IL as seen around
RTL expansion could more reliably produce the bad IL.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28831
--- Comment #36 from Richard Biener ---
Note that if we'd want to "preallocate" (or re-use) variables for argument
slots we have to properly arrange them according to the ABI. Consider
a function taking more than just a single argument [passed o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99703
--- Comment #7 from Richard Biener ---
(In reply to Worx from comment #6)
> (In reply to Richard Biener from comment #3)
> > Try --disable-cet as a workaround
>
> How apply this option ?
At configure time.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99694
Richard Biener changed:
What|Removed |Added
Summary|[9/10/11 Regression] gcc: |[9/10 Regression] gcc:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99712
Bug ID: 99712
Summary: Cannot elide aggregate parameter setup
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimiz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99718
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
--- Comment #2 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99718
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99719
Richard Biener changed:
What|Removed |Added
Target|x86_64-msys2-mingw-w64, |x86_64-msys2-mingw-w64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99720
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99721
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99721
--- Comment #3 from Richard Biener ---
So we end up scheduling
t.f90:1:16: note: node 0x35514b8 (max_nunits=1, refcnt=1)
t.f90:1:16: note: op: VEC_PERM_EXPR
t.f90:1:16: note: { }
t.f90:1:16: note: lane permutation { 0[0] 1[1] }
t.f90
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99721
--- Comment #4 from Richard Biener ---
Created attachment 50454
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50454&action=edit
patch
I'm testing this patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99721
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99724
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99726
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99727
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99728
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99739
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
--- Comment #1 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99744
--- Comment #1 from Richard Biener ---
it's difficult to check all requirements so elsewhere I suggested to be
forgiving when inlining always-inline functions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99746
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99746
--- Comment #8 from Richard Biener ---
I'm testing the following:
diff --git a/gcc/tree-vect-slp.c b/gcc/tree-vect-slp.c
index f1a2b5d60fa..762cba54bb5 100644
--- a/gcc/tree-vect-slp.c
+++ b/gcc/tree-vect-slp.c
@@ -3770,6 +3770,20 @@ vect_slp_an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99746
--- Comment #11 from Richard Biener ---
(In reply to Tamar Christina from comment #7)
> the problem starts because it marks _50 as hybrid, but don't see why it
> thinks that...
Because
t.f:36:16: note: Processing hybrid candidate : IMAGPART_E
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99746
--- Comment #12 from Richard Biener ---
Btw, the following also works as a fix but obviously I'm not in a position to
fully evaluate this. That said, hybrid SLP detection was rewritten during
SLP pattern development so the requirement to hook th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99751
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99751
Richard Biener changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99751
Richard Biener changed:
What|Removed |Added
Component|tree-optimization |ipa
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99751
--- Comment #5 from Richard Biener ---
parm 0 flags: nodirectescape
void e (int * d)
{
int * * c.0_1;
int * _2;
:
c.0_1 = c;
_2 = b (d_4(D));
*c.0_1 = _2;
return;
is wrong, it does escape through the *c store. I suppose b (d)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65847
--- Comment #3 from Richard Biener ---
Similarly
struct X { int a; int b; int c; int d; };
struct X foo (struct X x, struct X y)
{
struct X res;
res.a = x.a + y.a;
res.b = x.b + y.b;
res.c = x.c + y.c;
res.d = x.d + y.d;
return res;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98834
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98834
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99755
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99746
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96582
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99767
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |9.4
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99767
Richard Biener changed:
What|Removed |Added
Keywords|ice-on-invalid-code |ice-on-valid-code
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99768
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98209
Richard Biener changed:
What|Removed |Added
Summary|[8/9/10/11 Regression] |[8/9/10 Regression] printf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41953
Richard Biener changed:
What|Removed |Added
Last reconfirmed|2009-11-06 10:02:19 |2021-3-25
--- Comment #5 from Richard B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41898
--- Comment #5 from Richard Biener ---
Possibly related (implementation-wise) are ideas to handle array element
contents field-sensitive but not elements, thus have for
T p[10];
fields for members of 'T' but re-use the appropriate member for ea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19831
--- Comment #20 from Richard Biener ---
The original cases are all fixed but what remains is us failing to elide
void f ()
{
void *p = __builtin_malloc (1);
if (!p)
__builtin_abort ();
__builtin_free (p);
}
if that's even desirable.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27214
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27039
Bug 27039 depends on bug 27214, which changed state.
Bug 27214 Summary: The C frontend introduces undefined pointer overflow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27214
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99772
Richard Biener changed:
What|Removed |Added
Severity|normal |enhancement
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99776
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2021-03-26
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99776
--- Comment #2 from Richard Biener ---
diff --git a/gcc/match.pd b/gcc/match.pd
index 036f92fa959..61c93b5edd1 100644
--- a/gcc/match.pd
+++ b/gcc/match.pd
@@ -6168,9 +6168,12 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
(simplify
(BIT_FIELD_REF CO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99778
Richard Biener changed:
What|Removed |Added
Known to fail||11.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99780
--- Comment #2 from Richard Biener ---
It looks like the targetclone pass leaving the IL in broken state. The error
also looks bogus.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99781
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99785
Richard Biener changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
V
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99785
--- Comment #11 from Richard Biener ---
Btw, GCC 10 branch tip with -O1:
ipa inlining heuristics: 962.91 ( 85%) 0.39 ( 4%) 971.66 ( 84%)
1103801 kB ( 10%)
alias stmt walking : 40.95 ( 4%) 1.07 ( 11%) 42.13 (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99787
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99786
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99785
--- Comment #12 from Richard Biener ---
(In reply to Richard Biener from comment #11)
> Btw, GCC 10 branch tip with -O1:
>
> ipa inlining heuristics: 962.91 ( 85%) 0.39 ( 4%) 971.66 (
> 84%) 1103801 kB ( 10%)
> alias stmt walkin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99785
--- Comment #13 from Richard Biener ---
On trunk (with release checking) at -O2 the situation is not different from -O1
or the GCC 10 branch (so it's not 4 hours), the profile looks the same as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99447
Richard Biener changed:
What|Removed |Added
Resolution|WORKSFORME |---
Assignee|unassigned at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99788
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2021-03-26
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99788
Richard Biener changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99793
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99802
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99808
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2021-03-29
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99807
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99810
--- Comment #2 from Richard Biener ---
mdreorg turns
(insn 5 2 18 2 (set (reg:DI 2 r2)
(const_int -62135769600 [0xfff1886b6600])) "t.c":2:5 251
{*arm_movdi}
(nil))
into
(insn 5 2 18 (set (reg:DI 2 r2)
(mem:DI (label_re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99807
--- Comment #3 from Richard Biener ---
Just to say we currently require a ("random") SLP_TREE_REPRESENTATIVE even on
VEC_PERM_EXPR SLP nodes. With the testcase the choosen one is no longer
explicitely referenced and thus it does not get marked b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99807
--- Comment #4 from Richard Biener ---
(In reply to Richard Biener from comment #3)
> Just to say we currently require a ("random") SLP_TREE_REPRESENTATIVE even on
> VEC_PERM_EXPR SLP nodes. With the testcase the choosen one is no longer
> expli
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99807
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98642
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93711
Bug 93711 depends on bug 98642, which changed state.
Bug 98642 Summary: [10 Regression] wrong "use of deleted function" error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98642
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90254
Bug 90254 depends on bug 98642, which changed state.
Bug 98642 Summary: [10 Regression] wrong "use of deleted function" error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98642
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99318
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99062
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99816
Richard Biener changed:
What|Removed |Added
Keywords||wrong-debug
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43361
--- Comment #15 from Richard Biener ---
(In reply to Martin Sebor from comment #14)
> Reconfirmed with GCC 11 and the C test case below:
>
> void f (int);
>
> int main () {
> int i;
> int array[10];
> for (; i<10; ++i) {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99447
--- Comment #17 from Richard Biener ---
(In reply to Jan Hubicka from comment #15)
> I also tried to reproduce this locally w/o luck.
>
> Looking at the backtrace in detail, there is no DEF_STMT involved. It walks
> from dwarf dies, to RTL cons
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
Richard Biener changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #3 from Richard Bie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |10.3
Version|11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
--- Comment #4 from Richard Biener ---
OK, so I guess that things go wrong in wi::min_value where we nowhere check
that the precision we're asking for (384) fits in a wide_int,
WIDE_INT_MAX_PRECISION should be 160 (MAX_BITSIZE_MODE_ANY_INT) round
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
--- Comment #7 from Richard Biener ---
So we're value-numbering a char load
Value numbering stmt = _177 = *sc_175;
with sc_175 == _7 and
_7 = &cx_41(D)->i2c_adap[i_24].name;
which get's us a valueized ref (of type 'char') that looks like
cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
--- Comment #8 from Richard Biener ---
(In reply to Martin Liška from comment #6)
> > diff --git a/gcc/stor-layout.c b/gcc/stor-layout.c
> > index 784f131ebb8..94b8b21c7a8 100644
> > --- a/gcc/stor-layout.c
> > +++ b/gcc/stor-layout.c
> > @@ -283
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
Richard Biener changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #9 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99826
Bug ID: 99826
Summary: GIMPLE FE fails to grok pointer declarators
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99826
--- Comment #1 from Richard Biener ---
__GIMPLE(ssa) char * foo(char *p) {..}
works for the first issue. I failed to make the "late" __GIMPLE spec work in
a straight-forward manner. I guess we might want to change the default dumping
to prefer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99827
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |10.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99823
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
201 - 300 of 21963 matches
Mail list logo