https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-04-24
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109594
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109595
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109596
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109598
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602
Arsen Arsenović changed:
What|Removed |Added
CC||arsen at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #48 from Andrew Church ---
(In reply to rusty from comment #47)
> Civility please.
I have no intention of trying to start a fight :) Like you, I'm just trying to
improve the situation, and knowing that in my own open-source work I'm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109603
Bug ID: 109603
Summary: Vectorization failure for a small loop containing a
simple branch
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #49 from Jakub Jelinek ---
All that means is for APIs for which cast to void as silencing is meant to be
ok should be using [[nodiscard]] rather than
__attribute__((warn_unused_result)). APIs which do not want that should keep
using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
Bug ID: 109604
Summary: ice during GIMPLE pass: phiopt
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #50 from Florian Weimer ---
(In reply to Jakub Jelinek from comment #49)
> All that means is for APIs for which cast to void as silencing is meant to
> be ok should be using [[nodiscard]] rather than
> __attribute__((warn_unused_resul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
Richard Biener changed:
What|Removed |Added
Component|c |tree-optimization
Target Milestone|-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109603
Richard Biener changed:
What|Removed |Added
Blocks||53947
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109585
--- Comment #19 from Alexander Monakov ---
Manually minimized testcase for investigation, miscompiled at -O2:
struct P {
long v;
struct P *n;
};
struct F {
long x;
struct P fam[];
};
int f(struct F *f, int i)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109585
Jakub Jelinek changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #51 from Segher Boessenkool ---
(In reply to rusty from comment #47)
> Civility please.
Thank you.
> As Andrew Pinski says "people are mis-using this attribute", and Jakub
> Jelinek makes a similar point. The use of _wur has change
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #7 from Sebastian Huber ---
(In reply to Jakub Jelinek from comment #6)
> How have you configured gcc? I certainly can't reproduce this with
> --enable-targets=powerpc64-linux,powerpc-linux --with-cpu-32=power7
> --with-cpu-64=power
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583
--- Comment #4 from Martin Liška ---
Fixed now?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109583
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #52 from Jan Engelhardt ---
>This is useful for functions where not checking the
>result is either a security problem or always a bug, such as
>'realloc'.
always? reall..y..oc?
void *x = malloc(1);
realloc(x, 0);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109594
--- Comment #2 from Richard Biener ---
This goes wrong in update_address_taken before into-SSA which removes
TREE_ADDRESSABLE from 'v' without transforming it in any way.
:
D.3193 = VIEW_CONVERT_EXPR(v)[18446744073709551615];
return D.3193;
u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109406
--- Comment #2 from CVS Commits ---
The master branch has been updated by Kyrylo Tkachov :
https://gcc.gnu.org/g:9fd4a38c2f30b72ad5e3df7acb1ade201d8ac2cd
commit r14-193-g9fd4a38c2f30b72ad5e3df7acb1ade201d8ac2cd
Author: Kyrylo Tkachov
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109406
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Mileston
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 109406, which changed state.
Bug 109406 Summary: Missing use of aarch64 SVE2 unpredicated integer multiply
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109406
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #8 from Jakub Jelinek ---
Ah, --target powerpc-rtems6 reproduces it, wonder what is different here.
Reduced testcase:
void
foo (double x)
{
union { double d; unsigned i; } u;
u.d = x;
if (u.i & 2146435072)
return;
else
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #53 from Andrew Church ---
(In reply to Segher Boessenkool from comment #51)
> And that is the core of why this issue reinflames once in a while: some
> people
> abuse the attribute, and the compiler cannot read minds.
Ah, for a mind
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66207
--- Comment #10 from Uroš Bizjak ---
(In reply to Uroš Bizjak from comment #6)
> So, LRA testresults are clean on alphaev68-linux-gnu.
Please note that the above applies to alpha*EV6*, not plain alpha.
Plain alpha is !BWX architecture and uses
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2023-04-24
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109598
Martin Liška changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109605
Bug ID: 109605
Summary: -fno-tree-vectorize does not disable vectorizer
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109585
--- Comment #21 from Richard Biener ---
aliasing_component_refs_p seems to try handle trailing arrays via
component_ref_to_zero_sized_trailing_array_p. It properly detects
f_5->fam[0].n
but fails on
MEM[(struct P *)f_3(D) + 8B].n
but it wou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
Martin Liška changed:
What|Removed |Added
Summary|[14 Regression] ice during |[14 Regression] ICE during
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66207
--- Comment #11 from Richard Biener ---
I wonder if we can for simplicity deprecate non EV6 ... does any other existing
architecture use this functionality?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66207
--- Comment #12 from Uroš Bizjak ---
(In reply to Uroš Bizjak from comment #10)
> (In reply to Uroš Bizjak from comment #6)
> > So, LRA testresults are clean on alphaev68-linux-gnu.
>
> Please note that the above applies to alpha*EV6*, not plain
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #10 from Jakub Jelinek ---
Ah, but that actually isn't the problem, rather just useless clutter.
The problem is that
(jump_insn 10 7 32 2 (parallel [
(set (pc)
(if_then_else (eq (and:DI (reg:DI 9 9 [121])
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109543
--- Comment #2 from avieira at gcc dot gnu.org ---
Sorry for the delay. Here's the typedefs with GNU vectors.
typedef struct
{
float __attribute__ ((vector_size(16))) v[2];
} STRUCT;
#ifdef GOOD
typedef STRUCT TYPE;
#else
typedef union
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66207
--- Comment #13 from Uroš Bizjak ---
(In reply to Richard Biener from comment #11)
> I wonder if we can for simplicity deprecate non EV6 ... does any other
> existing architecture use this functionality?
To be more precise: is there a target tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109543
--- Comment #3 from avieira at gcc dot gnu.org ---
Err that should be 'double d[4];' so:
typedef struct
{
float __attribute__ ((vector_size(16))) v[2];
} STRUCT;
#ifdef GOOD
typedef STRUCT TYPE;
#else
typedef union
{
STRUCT s;
doubl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109605
Richard Biener changed:
What|Removed |Added
Component|tree-optimization |driver
--- Comment #1 from Richard Bie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109587
--- Comment #4 from Tamar Christina ---
(In reply to Richard Biener from comment #3)
> The issue isn't unrolling but invariant motion. We unroll the innermost
> loop, vectorizer the middle loop and then unroll that as well. That leaves
> us wi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #11 from Jakub Jelinek ---
I bet the culprit is that *rotl3_mask_dot has
(mode == Pmode || UINTVAL (operands[3]) <= 0x7fff)
in condition. So, because *branch_anddi3_dot always wants DImode, if Pmode is
SImode,
it should make sur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #12 from Jakub Jelinek ---
--- gcc/config/rs6000/rs6000.cc.jj 2023-04-04 10:33:47.433201866 +0200
+++ gcc/config/rs6000/rs6000.cc 2023-04-24 12:31:07.237031550 +0200
@@ -11409,7 +11409,16 @@ bool
rs6000_is_valid_rotate_dot_mask
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109587
--- Comment #5 from Richard Biener ---
(In reply to Tamar Christina from comment #4)
> (In reply to Richard Biener from comment #3)
> > The issue isn't unrolling but invariant motion. We unroll the innermost
> > loop, vectorizer the middle loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
Jakub Jelinek changed:
What|Removed |Added
Summary|[13/14 Regression] powerpc: |[12/13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #14 from Jakub Jelinek ---
Created attachment 54910
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54910&action=edit
gcc13-pr109566.patch
Full test I'm going to bootstrap/regtest momentarily.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109606
Bug ID: 109606
Summary: Unguarded `__is_same` builtin usage
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109566
--- Comment #15 from Sebastian Huber ---
Thanks for digging into this. With the change I am able to build the
powerpc-rtems target.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109587
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109585
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=109587
--- Comment #7 from Tamar Christina ---
(In reply to Richard Biener from comment #5)
> (In reply to Tamar Christina from comment #4)
> > (In reply to Richard Biener from comment #3)
> > > The issue isn't unrolling but invariant motion. We unrol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Assignee|un
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #4 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602
--- Comment #5 from Romain Geissler ---
Hi,
My intention was to try to raise upstream an issue that people packaging gcc
may hit in some cases. Gentoo has such a patch, but I also have a similar one
on my side since couple of years, it's only y
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109607
Bug ID: 109607
Summary: IPA replaces stmt with invalid gimple
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109607
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-04-24
Assignee|unassign
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109606
--- Comment #1 from Jonathan Wakely ---
(In reply to Alexander from comment #0)
> This commit
> (https://github.com/gcc-mirror/gcc/commit/
> 17855eed7fc76b2cee7fbbc26f84d3c8b99be13c) introduces new helper function
> `__find_uniq_type_in_pack` th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109606
--- Comment #2 from Jonathan Wakely ---
P.S. the reason it uses __is_same instead of std::is_same_v is because it is
C++14 code, and the reason it doesn't use std::is_same<>::value is to avoid the
class template instantiation.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109606
--- Comment #3 from Alexander ---
(In reply to Jonathan Wakely from comment #1)
> Yes. Using libstdc++ headers with older **or newer** versions of GCC is
> completely unsupported. For other compilers, they need to be sufficiently
> close to GCC,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109589
--- Comment #5 from seurer at gcc dot gnu.org ---
I've seen some successful builds go by on the old systems. Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109606
--- Comment #4 from Alexander ---
^ I meant `__is_same`, not `__same_as` (typo)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523
David Brown changed:
What|Removed |Added
CC||david at westcontrol dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
--- Comment #2 from Andrew Pinski ---
I had already posted a fix for this (and approved already):
https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616499.html
I will add the testcase.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
--- Comment #3 from David Binderman ---
Another test case, this time in C++:
struct {
int second;
} selectPlayer_playerRes;
int selectPlayer_playerRes_0;
int selectPlayer() {
if (selectPlayer_playerRes_0 && selectPlayer_playerRes.second >=
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109606
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:2f58dd71d1b8e23f28a43360742519e92ee0c8d5
commit r14-199-g2f58dd71d1b8e23f28a43360742519e92ee0c8d5
Author: Andrew Pinski
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68894
--- Comment #10 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:7049241f6ee558cfc0b227b5a0a355ec29afd6f1
commit r14-201-g7049241f6ee558cfc0b227b5a0a355ec29afd6f1
Author: Andrew Pinski
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109604
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68894
--- Comment #11 from Andrew Pinski ---
The phiopt issue is fixed for GCC 14 now.
Ifcvt will be fixed soon.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103931
--- Comment #17 from Bernhard Reutner-Fischer ---
(In reply to Bernhard Reutner-Fischer from comment #16)
> I'm testing a more elaborate test which keeps check_for_ambiguous in the
> same spot as before, but in that check, looks if the symtree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109608
Bug ID: 109608
Summary: [14 regression] net test case
g++.dg/cpp0x/constexpr-pmf3.C in
r10-11306-gda17a9049ee0a8 has excess errors
Product: gcc
Version: 10.4.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103931
--- Comment #18 from Bernhard Reutner-Fischer ---
(In reply to Bernhard Reutner-Fischer from comment #17)
> (In reply to Bernhard Reutner-Fischer from comment #16)
>
> > I'm testing a more elaborate test which keeps check_for_ambiguous in the
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109580
--- Comment #2 from David Malcolm ---
The warning is emitted on this statement:
_23 = _3 | _5;
within this basic block in the optimized code:
[local count: 217325344]:
nfd_26 = emacs_open_noquit ("/dev/null", 2, 0);
_3 = nfd_26 < 0;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109580
--- Comment #3 from David Malcolm ---
The optimized stmt with UNKNOWN_LOCATION is created from:
(gdb) call inform(stmt->location, "stmt in gimple_simplify")
../../src/pr109580.c:10:9: note: stmt in gimple_simplify
10 | err |= dup2(nfd, 0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109580
David Malcolm changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109598
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Summary|ICE: tree check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523
Georg-Johann Lay changed:
What|Removed |Added
CC||gjl at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68894
--- Comment #12 from Andrew Pinski ---
Just a quick note on this part of the bug report:
(In reply to Richard Biener from comment #3)
> Doing this in a classical way in phi-opt might end up being slightly
> convoluted.
> So I'd propose to try to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
Bug ID: 109609
Summary: Invalid strncpy/strncat optimization in GCC 12
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
--- Comment #1 from Andrew Pinski ---
Note strcpy arguments cannot be overlapping if the dst overlaps with the src,
then the behavior is undefined. I think you are hitting that undefined behavior
here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> Note strcpy arguments cannot be overlapping if the dst overlaps with the
> src, then the behavior is undefined. I think you are hitting that undefined
> behavior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109610
Bug ID: 109610
Summary: [14 regression] gcc.target/powerpc/dform-3.c fails
after
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
Arsen Arsenović changed:
What|Removed |Added
CC||romain.geissler at amadeus dot
com
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109602
Arsen Arsenović changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |12.3
Summary|Invalid strncpy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
--- Comment #4 from Andrew Pinski ---
Oh the problem is related to tail calls:
strncpy (&dst, ptr_30, 23); [tail call]
That should not be marked as a tail call as buf is still alive during the call
of strncpy.
Simple workaround, add
asm("":
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
--- Comment #5 from Jakub Jelinek ---
Yeah, exactly, the difference between the two revisions is first in tailc pass:
--- pr109609.C.202t.tailc_ 2023-04-24 15:48:33.0 -0400
+++ pr109609.C.202t.tailc 2023-04-24 15:49:08.000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
Arsen Arsenović changed:
What|Removed |Added
CC||arsen at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
--- Comment #6 from Andrew Pinski ---
Note, changing `ptr < buf` to `ptr != buf` still invokes the wrong code being
generated.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103931
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=109609
--- Comment #7 from Gabriel Burca ---
Here's the code that still fails with -O3 -fno-optimize-sibling-calls:
```
#include
#include
#define N 23
#define MAX_LEN 13
char dst[N + 1];
void stringify(uint64_t id) {
char buf[MAX_LEN];
char *pt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109609
--- Comment #8 from Jakub Jelinek ---
In that case it started with r12-382-ged3c43224cc4e378d
But maybe it would be better to track it separately.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109611
Bug ID: 109611
Summary: Missing -Wrestrict across TUs (even with LTO)
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109611
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Keywords|
bin/gcc -v
Using built-in specs.
COLLECT_GCC=/home/dcb36/gcc/results/bin/gcc
COLLECT_LTO_WRAPPER=/home/dcb36/gcc/results.20230424.asan.ubsan/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../trunk.year/configure
--prefix=/home/dcb36/gcc/results.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109590
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109613
Bug ID: 109613
Summary: -Wanalyzer-null-dereference false positive involving
__builtin_unreachable
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678
Sam James changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678
--- Comment #17 from Sam James ---
(In reply to David Brown from comment #15)
> This has been implemented in gcc 10, and -fno-common is now the default.
> This "bug" can presumably now be closed.
>
> Many thanks to the gcc developers here.
Don
1 - 100 of 125 matches
Mail list logo
