https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
--- Comment #5 from Andrew Pinski ---
I am 99% sure there is aliasing violations in this code too:
#if _MSC_VER
#define GETU32(p) SWAP(*((u32 *)(p)))
#define PUTU32(ct, st) \
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
--- Comment #4 from Martin Liška ---
(In reply to Andrew Pinski from comment #2)
> Also does adding -fno-strict-aliasing help?
Yes, it helps.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
--- Comment #3 from Martin Liška ---
(In reply to Andrew Pinski from comment #1)
> We need a better testcase than the direction on how to build a full package.
Sure, I'll try to reduce it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108710
Bug ID: 108710
Summary: Recognizing "rounding down to the nearest power of
two"
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108709
--- Comment #1 from nightstrike ---
Perhaps these are separate bugs, but:
1) gcc.dg/analyzer/pipe-manpages.c will need similar improvements
2) gcc.dg/analyzer/pipe-void-return.c passes with an incorrect declaration for
pipe(), implying that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108709
Bug ID: 108709
Summary: FAIL: gcc.dg/analyzer/pipe-glibc.c
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108705
--- Comment #1 from Rimvydas (RJ) ---
Using assumed shape arrays "p(:),s(:)" in bar() requires longer chain of calls
to foo() and all time spent moves to "tree VRP", but produced assembly is more
cluttered than with assumed size array
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108708
Bug ID: 108708
Summary: __analyzer_dump_named_constant fails with derived
values
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108707
Hongtao.liu changed:
What|Removed |Added
Target||x86_64-*-* i?86-*-*
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108707
Bug ID: 108707
Summary: suboptimal allocation with same memory op for many
different instructions.
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108706
Bug ID: 108706
Summary: [13 Regression] Indefinite recursion when compiling
gcc/testsuite/g++.dg/cpp23/static-operator-call5.C w/
-g
Product: gcc
Version: 13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107602
--- Comment #2 from nightstrike ---
Better link(In reply to nightstrike from comment #1)
> Reverting 186d43a78e945ebe9fbe217fc341847af7f95d30 fixes this problem at
> least for me
Better link: r255433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107602
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108705
Andrew Pinski changed:
What|Removed |Added
Keywords||compile-time-hog
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108705
Bug ID: 108705
Summary: Unexpected CPU time usage with LTO in ranger
propagation
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108704
--- Comment #2 from David Malcolm ---
Adding -fno-analyzer-state-purge fixes the false positive, looks like it's
erroneously pruning the value of fp0 immediately after the first assignment.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108704
David Malcolm changed:
What|Removed |Added
Target Milestone|--- |13.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108704
Bug ID: 108704
Summary: Many -Wanalyzer-use-of-uninitialized-value false
positives seen in qemu's softfloat.c
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854
--- Comment #145 from lucier at math dot purdue.edu ---
Created attachment 54424
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54424=edit
CPU and Memory usage reports for mainline 13.0.1 (mainline)
Thank you for looking at this issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108694
--- Comment #4 from Bruno Haible ---
(In reply to Aaron Ballman from comment #3)
OK. So, except for this unlucky (*) choice of attribution in case of a conflict
between function declaration and function definition, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108661
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69636
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108661
--- Comment #2 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:c300e251f5b22d15b126f3c643cd55a119994e48
commit r13-5733-gc300e251f5b22d15b126f3c643cd55a119994e48
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108689
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:c300e251f5b22d15b126f3c643cd55a119994e48
commit r13-5733-gc300e251f5b22d15b126f3c643cd55a119994e48
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107079
--- Comment #4 from Marek Polacek ---
The ICE could be fixed with
--- a/gcc/cp/call.cc
+++ b/gcc/cp/call.cc
@@ -13604,9 +13604,13 @@ set_up_extended_ref_temp (tree decl, tree expr,
vec **cleanups,
init = NULL_TREE;
}
else
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108694
--- Comment #3 from Aaron Ballman ---
(In reply to Bruno Haible from comment #2)
> But '-Wdeprecated-non-prototype' does not exactly have the behaviour you
> want: while it warns for 'func1 (1);' and 'func3 (3);' (good!), it warns
> also for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108694
--- Comment #2 from Bruno Haible ---
(In reply to Florian Weimer from comment #1)
> “()” is going to be fine when matched with an empty parameter list in a
> definition, or an empty argument list in a call. I don't think it's
> necessary to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108693
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Andrew Pinski
:
https://gcc.gnu.org/g:6f23c9077feebb29c2a28ffe89b287286df27d6d
commit r12-9114-g6f23c9077feebb29c2a28ffe89b287286df27d6d
Author: Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
Siddhesh Poyarekar changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
--- Comment #10 from Andrew Pinski ---
(In reply to Jakub Jelinek from comment #9)
> I think that is how inline asm always behaved. If it is not ok to be DCEd
> when the result is dead, one needs to use volatile keyword.
Oh you are right I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Siddhesh Poyarekar
:
https://gcc.gnu.org/g:45b346664c0af57053e77276cd030015eb21f851
commit r12-9113-g45b346664c0af57053e77276cd030015eb21f851
Author: Siddhesh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Siddhesh Poyarekar
:
https://gcc.gnu.org/g:4526562a305b3bfc18485a2aa017500aa22aa14b
commit r12-9112-g4526562a305b3bfc18485a2aa017500aa22aa14b
Author: Siddhesh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #5 from Aldy Hernandez ---
(In reply to Richard Biener from comment #3)
> But yes, your observation about m_has_cache_entry is correct - if that has
> any value (it makes reset_path "cheap"), then it should be also relied on
> upon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
--- Comment #3 from Jakub Jelinek ---
I mean in mangling...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
--- Comment #2 from Jakub Jelinek ---
Created attachment 54423
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54423=edit
gcc13-pr108698.patch
Actually, if it is just EXCESS_PRECISION_EXPR around REAL_CST, that one can be
handled easily
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103259
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108703
Bug ID: 108703
Summary: ICE: in extract_constrain_insn, at recog.cc:2692 (insn
does not satisfy its constraints: movhi_insn) on
sparc64 at -O1
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108690
--- Comment #2 from Sam James ---
Please add https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108694 to See Also.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
--- Comment #7 from Andrew Pinski ---
(In reply to Andrew Macleod from comment #6)
> Fixes the issue... huh how long has THAT been there
Since r8-5124-g23ffbafe3a39 when simple_dce_from_worklist was added. Though
simple_dce_from_worklist
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
--- Comment #6 from Andrew Macleod ---
diff --git a/gcc/tree-ssa-dce.cc b/gcc/tree-ssa-dce.cc
index b2fe9f4f55e..752785541e4 100644
--- a/gcc/tree-ssa-dce.cc
+++ b/gcc/tree-ssa-dce.cc
@@ -2140,6 +2140,7 @@ simple_dce_from_worklist (bitmap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
Andrew Pinski changed:
What|Removed |Added
Summary|[13 Regression] ICE:|[12/13 Regression] ICE:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
--- Comment #11 from apjo at tuta dot io ---
(In reply to Andrew Pinski from comment #10)
Okay now that looks like a clang bug. Clang is supposed to diagnose misleading
indentation like that (see: https://godbolt.org/z/1fv4rEseo).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108702
Bug ID: 108702
Summary: [13 Regression] ICE in get_partitioning_class, at
symtab.cc:2096
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
--- Comment #4 from Andrew Pinski ---
Hmm, simple_dce_from_worklist. It might be the case you could hit this issue
without VRP then ...
Let me try.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
--- Comment #10 from Andrew Pinski ---
That is clang does not warn about this case here (changed all tabs to spaces to
indepdent of -ftabstop option):
```
int randBytesGet()
{
int t;
while (true) {
if (true)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
--- Comment #3 from Andrew Macleod ---
OK, its been a while. Why is there a VUSE on the return? this is the IL
right from into-ssa:
int f (int a)
{
int _4;
:
# .MEM_2 = VDEF <.MEM_1(D)>
__asm__(" " : "=X" a_3 : : "memory");
if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
Andrew Pinski changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
apjo at tuta dot io changed:
What|Removed |Added
Resolution|INVALID |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95107
--- Comment #11 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:c36f3da534e7f411c5bc48c5b6b660e238167480
commit r13-5732-gc36f3da534e7f411c5bc48c5b6b660e238167480
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108657
--- Comment #11 from Mikael Pettersson ---
Bisected on x86_64-linux-gnu:
dc477ffb4aba21e9cf47de22a4df6f2b23849505 is the first bad commit
commit dc477ffb4aba21e9cf47de22a4df6f2b23849505
Author: Richard Biener
Date: Thu Jul 21 10:13:46 2022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108700
--- Comment #3 from Andreas Schwab ---
The grammar doesn't tell everything, though currently only storage-class
specifiers are expected to occur at the beginning.
>From c-parser.cc:c_parser_declspecs:
/* TODO: Distinguish between
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
Andrew Pinski changed:
What|Removed |Added
Resolution|FIXED |INVALID
--- Comment #7 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
apjo at tuta dot io changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #6 from apjo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
Andrew Pinski changed:
What|Removed |Added
Resolution|FIXED |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
apjo at tuta dot io changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #5 from apjo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
--- Comment #4 from Andrew Pinski ---
Also once you change godbolt to be 8 spaces/tab, it becomes obvious the warning
is correct for the default.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
--- Comment #1 from Andrew Pinski ---
Created attachment 54421
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54421=edit
testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701
Bug ID: 108701
Summary: Incorrect -Wmisleading-indentation
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
--- Comment #1 from Jakub Jelinek ---
Simpler testcase:
template
decltype (T () * T () + 1.0) foo ()
{
return T () * T () + 1.0;
}
void
bar ()
{
foo ();
foo ();
foo ();
}
The question is if the excess precision should be visible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108694
Andrew Pinski changed:
What|Removed |Added
Target|x86_64-linux-gnu|
Host|x86_64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108700
--- Comment #2 from Vincent Lefèvre ---
And there's the same issue with "inline" instead of "_Noreturn" (these are the
only two function specifiers).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108700
--- Comment #1 from Andrew Pinski ---
This has been warning since _Noreturn support was added back in r177881 .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108316
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
Andrew Pinski changed:
What|Removed |Added
Keywords||lto
--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
Andrew Pinski changed:
What|Removed |Added
Status|NEW |WAITING
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108700
Bug ID: 108700
Summary: false _Noreturn error with
-Werror=old-style-declaration
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106656
--- Comment #4 from Marek Polacek ---
(In reply to Dimitrij Mijoski from comment #3)
> The documentation for CLI flag -fchar8_t should be updated
> https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html .
Oh right, this is not an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #4 from Aldy Hernandez ---
Created attachment 54420
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54420=edit
reuse path_range_query SSA cache for all of back_threader class
Off of the top of my head (i.e. probably very
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108699
Bug ID: 108699
Summary: gcc.c-torture/execute/builtin-bitops-1.c fails on
power 9 BE
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108692
--- Comment #3 from Jakub Jelinek ---
Created attachment 54419
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54419=edit
gcc13-pr108692.patch
Untested fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106656
Dimitrij Mijoski changed:
What|Removed |Added
CC||dmjpp at hotmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #3 from Richard Biener ---
But yes, your observation about m_has_cache_entry is correct - if that has any
value (it makes reset_path "cheap"), then it should be also relied on upon
growth. Maybe make this bitmap an optional feature
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #2 from Richard Biener ---
Created attachment 54418
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54418=edit
replace vector with hash_map
it's the clearing that shows up on the profile, I've experimented with the
attached
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #1 from Aldy Hernandez ---
Sharing a cache with say the ranger is a no go, because the path_range_query's
cache is specific to the path, but perhaps we could share the path's cache
between constructions providing a constructor that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108692
--- Comment #2 from Jakub Jelinek ---
So, on simplified -O2 -ftree-vectorize testcase with trunk:
int
foo (signed char *x, signed char *y, int n)
{
int i, r = 0;
signed char a, b;
for (i = 0; i < n; i++)
{
a = x[i];
b =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
Martin Liška changed:
What|Removed |Added
Target Milestone|--- |13.0
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
Bug ID: 108698
Summary: [13 Regression] decltype ((T() +
‘excess_precision_expr’ not supported by
dump_expr)) median(ndarray) [with
T = double]’: since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108691
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=108688
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108685
Richard Biener changed:
What|Removed |Added
Keywords||ice-checking
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103541
--- Comment #5 from CVS Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:f661c0bb6371f355966a67b5ce71398e80792948
commit r13-5730-gf661c0bb6371f355966a67b5ce71398e80792948
Author: Vladimir N. Makarov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108692
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854
--- Comment #144 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:295adfc9ed20468cdaba3afe258d57b58a8df792
commit r13-5729-g295adfc9ed20468cdaba3afe258d57b58a8df792
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
Bug ID: 108697
Summary: constructing a path-range-query is expensive
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108696
Bug ID: 108696
Summary: querying relations is slow
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2023-02-07
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
Bug ID: 108695
Summary: [13 Regression] Wrong code since
r13-5215-gb1f30bf42d8d47 for dd_rescue package
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108694
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106809
--- Comment #14 from CVS Commits ---
The releases/gcc-10 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:051f78a5c1d6994c10ee7c35453ff0ccee94e5c6
commit r10-11201-g051f78a5c1d6994c10ee7c35453ff0ccee94e5c6
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108646
--- Comment #5 from Jonny Grant ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Jonny Grant from comment #3)
> > Is it worth -Wnonnull emitting a warning message that it needs optimization
> > to get the needed data flow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106809
--- Comment #13 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:5125737077adc2110b9f17f06141e8f76ccab9b9
commit r11-10510-g5125737077adc2110b9f17f06141e8f76ccab9b9
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108694
Bug ID: 108694
Summary: need a new warning option for preparing migration to
ISO C 23
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108692
--- Comment #1 from Jakub Jelinek ---
Before the r11-5160 change, the innermost loop was an unsigned char x 16 -> int
x 4
SAD_EXPR:
[local count: 567644343]:
# vect_var12_i_49.13_90 = PHI
# ivtmp.57_149 = PHI
vect_var32_32.16_95 =
1 - 100 of 118 matches
Mail list logo
