https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103126
Bug ID: 103126
Summary: Miss vectorization for bit_and/bit_ior/bit_xor
reduction
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #13 from Aldy Hernandez ---
Since DOM is the only threading pass that keeps more or less accurate
profiling data, here's a very wild guess.
The pre-loop DOM threading pass does not thread some paths because of
the restrictions in pl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103102
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103107
Martin Liška changed:
What|Removed |Added
Summary|[12 Regression] ICE: tree |[12 Regression] ICE: tree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102831
Eric Botcazou changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86389
--- Comment #13 from Richard Biener ---
(In reply to Jan Hubicka from comment #12)
> Since the vector_subscript testcase seems indeed to be frontend issue
> triggered by -fipa-pta (and soon by modref). I wonder if we should have
> fortran bug tra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103012
Martin Liška changed:
What|Removed |Added
CC||nathan at gcc dot gnu.org
Keyw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102906
Aldy Hernandez changed:
What|Removed |Added
Component|middle-end |testsuite
--- Comment #7 from Aldy Her
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103116
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103122
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Summary|[12 Regression] ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103119
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103093
Martin Liška changed:
What|Removed |Added
CC||vsevolod.livinskij at frtk dot
ru
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103035
Bug 103035 depends on bug 103119, which changed state.
Bug 103119 Summary: ICE in get_imports, at gimple-range-gori.cc:230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103119
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #14 from Martin Liška ---
I tend to close this issue due to a mismatch between train and reference run.
It's basically measuring speed of the cold code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #15 from rguenther at suse dot de ---
On Mon, 8 Nov 2021, aldyh at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
>
> --- Comment #13 from Aldy Hernandez ---
> Since DOM is the only threading pass tha
Note that it still seems to me that the crossed_loop_header handling is
overly conservative. We have:
@ -2771,6 +2771,7 @@ jt_path_registry::cancel_invalid_paths
(vec &path)
bool seen_latch = false;
int loops_crossed = 0;
bool crossed_latch = false;
+ bool crossed_loop_header = false;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #16 from hubicka at kam dot mff.cuni.cz ---
Note that it still seems to me that the crossed_loop_header handling is
overly conservative. We have:
@ -2771,6 +2771,7 @@ jt_path_registry::cancel_invalid_paths
(vec &path)
bool seen_l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
Aldy Hernandez changed:
What|Removed |Added
CC||jeffreyalaw at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103112
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103114
Martin Liška changed:
What|Removed |Added
Summary|[12 Regression] ICE in |[12 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99088
--- Comment #2 from Andrew Pinski ---
With -fno-checking, GCC compiling errors out really quickly.
Without -fno-checking on the trunk takes around 20s.
With -fno-checking on the trunk takes 1.2s.
I don't think there is anything to fix here real
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #18 from Aldy Hernandez ---
> If I read it correctly, for a path that enters the loop and later leaves
> it (where threading is desirable since we skip the whole loop) the logic
> above will still return true (after finishing the wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102906
--- Comment #8 from Aldy Hernandez ---
This may be related to the discussion in PR102997, particularly comment 16.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
Bug ID: 103127
Summary: ICE in fold_convert_loc, at fold-const.c:2573
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103096
--- Comment #8 from Andrew Pinski ---
No compiler I have tried does a decent job at figuring this testcase out
quickly (over 20s).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89259
Martin Liška changed:
What|Removed |Added
Keywords||patch
--- Comment #5 from Martin Liška -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89259
Martin Liška changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #19 from hubicka at kam dot mff.cuni.cz ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
>
> --- Comment #18 from Aldy Hernandez ---
>
> > If I read it correctly, for a path that enters the loop and later leaves
> > it (wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
Andrew Pinski changed:
What|Removed |Added
Component|tree-optimization |middle-end
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103127
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103123
--- Comment #4 from Vincent Lefèvre ---
(In reply to Andrew Pinski from comment #1)
> This is warning and can be turned off, -Woverflow is on by default.
The warning can be turned off, but there are 2 issues:
1. The message "floating constant
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103044
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103114
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
St
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103123
--- Comment #5 from Vincent Lefèvre ---
(In reply to Andrew Pinski from comment #3)
> Clang produces:
> :4:10: warning: magnitude of floating-point constant too large for
> type 'double'; maximum is 1.7976931348623157E+308 [-Wliteral-range]
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103102
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103105
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103107
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
--- Comment #2 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103114
--- Comment #4 from Richard Biener ---
Or always build+fold a COMPLEX_EXPR.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103107
--- Comment #3 from Martin Liška ---
(In reply to Richard Biener from comment #2)
> I think I've seen a duplicate.
You probably mean PR103099, but the suggested fix from the PR does not fix
this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103128
Bug ID: 103128
Summary: gcc/fortran/symbol.c:5112:1: warning: function
'gfc_get_ultimate_derived_super_type' is not needed
and will not be emitted
[-Wunneeded-inte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103114
--- Comment #5 from Jakub Jelinek ---
--- gcc/cp/parser.c.jj 2021-10-28 20:07:48.571193189 +0200
+++ gcc/cp/parser.c 2021-11-08 10:18:02.042896144 +0100
@@ -4804,9 +4804,9 @@ cp_parser_userdef_numeric_literal (cp_pa
else /* if (id_eq
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103129
Bug ID: 103129
Summary: gcc/diagnostic-show-locus.c:692:18: warning: unused
variable 'def_tabstop' [-Wunused-const-variable] since
g:bd5e882cf6e0def3dd1bc106075d59a303fe0d1e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102871
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-11-08
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103117
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120
Richard Biener changed:
What|Removed |Added
Severity|blocker |normal
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103117
--- Comment #2 from hubicka at kam dot mff.cuni.cz ---
> I suppose modref could (for pointer returns) use ranger to query its range
> and see if it ever is non-NULL? I'm not sure if we reliably propagate
> null pointer constants everywhere.
I t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102871
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57527
Andrew Pinski changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103121
--- Comment #1 from Richard Biener ---
grp_name = XALLOCAVEC (char, IDENTIFIER_LENGTH (complete_name) + 1);
so the array is at least of size 1. David, can you try adding
-fno-tree-vectorize to the command line to see if that silences the dia
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86426
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103122
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103128
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103123
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103126
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84796
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84857
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #20 from Richard Biener ---
(In reply to hubicka from comment #19)
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
> >
> > --- Comment #18 from Aldy Hernandez ---
> >
> > > If I read it correctly, for a path that enters th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103114
--- Comment #6 from rguenther at suse dot de ---
On Mon, 8 Nov 2021, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103114
>
> --- Comment #5 from Jakub Jelinek ---
> --- gcc/cp/parser.c.jj 2021-10-28 20:07:48
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103117
--- Comment #3 from rguenther at suse dot de ---
On Mon, 8 Nov 2021, hubicka at kam dot mff.cuni.cz wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103117
>
> --- Comment #2 from hubicka at kam dot mff.cuni.cz ---
> > I suppose modref co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101204
Thomas Schwinge changed:
What|Removed |Added
Assignee|msebor at gcc dot gnu.org |tschwinge at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102831
Thomas Schwinge changed:
What|Removed |Added
CC||tschwinge at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88683
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173
Andrew Pinski changed:
What|Removed |Added
CC||mjansche at google dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56665
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57470
--- Comment #2 from Andrew Pinski ---
So in GCC 10+ we produce:
: In instantiation of 'struct S':
:11:9: required from here
:8:32: error: incomplete type 'Incomplete' used in nested name
specifier
8 | static_assert(Incomplete::value, "");
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85548
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2018-11-22 00:00:00 |2021-11-8
--- Comment #3 from Andrew Pin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102831
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #2 from Thomas Schwinge ---
> Are you guys able to reliably reproduce the problem? Asking because for me,
> it
> was very flaky: some (seemingly random) change elsewhere
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85548
--- Comment #4 from Jonathan Wakely ---
__builtin_clear_padding is for libstdc++ to clear padding bits in arbitrary
trivially-copyable objects, it's not useful here because the compiler should be
doing it automatically.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102856
Thomas Schwinge changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102838
Thomas Schwinge changed:
What|Removed |Added
CC||jules at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103130
Bug ID: 103130
Summary: comments are parsed differently with -fdirectives-only
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103131
Bug ID: 103131
Summary: -Wpedantic doesn't warn about extra semicolons anymore
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103131
--- Comment #1 from Milian Wolff ---
correction: gcc version 10 and below used to complain
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103131
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96068
Andrew Pinski changed:
What|Removed |Added
CC||mail at milianw dot de
--- Comment #5 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103130
Andrew Pinski changed:
What|Removed |Added
Known to work||10.3.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103120
--- Comment #5 from Aldy Hernandez ---
This is an ordering issue in the path solver, and it's not even relation
related! How interesting.
./xgcc -B./ a.c -O2 -fdisable-tree-ethread -fdisable-tree-thread1
-fdisable-tree-thread2 -fdisable-tree-t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20785
--- Comment #14 from Pavel M ---
To: Vincent Lefèvre
Re: the warnings are useless.
The "warning: ignoring '#pragma STDC FENV_ACCESS' [-Wunknown-pragmas]" probably
needs to be generated by default (i.e. not with -Wall) because now gcc silently
mi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101636
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103132
Bug ID: 103132
Summary: ice: Segmentation fault
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: un
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101636
--- Comment #8 from Martin Liška ---
I can still reproduce it with the current master
(g:b7cd3946062e034bcc644db2569cd750041a2ee3):
$ gcc pr101636.c -c -mavx512f -O1 -ftree-vectorize -fno-vect-cost-model
pr101636.c: In function ‘bar’:
pr101636.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101636
--- Comment #9 from Martin Liška ---
Valgrind reports:
==9236== Conditional jump or move depends on uninitialised value(s)
==9236==at 0xA3EC2C: bitmap_clear_bit (sbitmap.h:153)
==9236==by 0xA3EC2C: verify_loop_structure() (cfgloop.c:157
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #21 from hubicka at kam dot mff.cuni.cz ---
> to also allow to thread through a loop path not crossing the latch but
> at least for the issue of "breaking loops" the loops_crossed stuff shouldn't
> be necessary. It might still preven
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103117
--- Comment #4 from hubicka at kam dot mff.cuni.cz ---
> > I don't know - this way we have separate dumps etc. I think mistake was
> > scheduling pure-const and later modref too late.
>
> Maybe. If you move them please put a comment before unc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103132
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-11-08
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103132
Martin Liška changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100520
--- Comment #8 from CVS Commits ---
The master branch has been updated by Martin Liska :
https://gcc.gnu.org/g:7553bd35c876efaf8ab0b6661a6102822b99e6e3
commit r12-4996-g7553bd35c876efaf8ab0b6661a6102822b99e6e3
Author: Martin Liska
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100520
Martin Liška changed:
What|Removed |Added
Known to fail|12.0|
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103107
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=103133
Bug ID: 103133
Summary: Binary built with -static using std::thread crashes
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100520
--- Comment #10 from CVS Commits ---
The releases/gcc-11 branch has been updated by Martin Liska
:
https://gcc.gnu.org/g:580d66f5a0bdcd88dcdab2d4ace3bbbaae121af3
commit r11-9221-g580d66f5a0bdcd88dcdab2d4ace3bbbaae121af3
Author: Martin Liska
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100520
Martin Liška changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20785
--- Comment #15 from Vincent Lefèvre ---
(In reply to Pavel M from comment #14)
> The "warning: ignoring '#pragma STDC FENV_ACCESS' [-Wunknown-pragmas]"
> probably needs to be generated by default
Getting the warning on "#pragma STDC FENV_ACCESS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #2 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101480
--- Comment #25 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:19dcea67ac40cfdeb396fa264ebbe04fbe61fdc0
commit r11-9222-g19dcea67ac40cfdeb396fa264ebbe04fbe61fdc0
Author: Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102139
--- Comment #11 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:7f04f47d8d414c399ce7b5c8158fadc437469755
commit r11-9224-g7f04f47d8d414c399ce7b5c8158fadc437469755
Author: Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102572
--- Comment #8 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:092e98d94080ca253dc4ef6957d6efaeccb88df6
commit r11-9225-g092e98d94080ca253dc4ef6957d6efaeccb88df6
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102788
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Known to fail|
1 - 100 of 241 matches
Mail list logo
