https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120079
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120079
Bug ID: 120079
Summary: RFE: -Wp,-dM equivalent for assertions
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: prepro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120078
Andrew Pinski changed:
What|Removed |Added
Component|c |middle-end
--- Comment #3 from Andrew P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120078
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.5
Summary|-Wjump-misses-i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120078
--- Comment #1 from Andrew Pinski ---
Actually wait it is enabled:
```
Wjump-misses-init
C ObjC Var(warn_jump_misses_init) Warning LangEnabledby(C ObjC,Wc++-compat)
Warn when a jump misses a variable initialization.
```
But I don't get a warni
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120078
Bug ID: 120078
Summary: -Wjump-misses-init should be enabled by -Wc++-compat
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87038
--- Comment #25 from Andrew Pinski ---
Note clang just added -Wjump-bypasses-init which does the exactly same as GCC's
-Wjump-misses-init (https://github.com/llvm/llvm-project/pull/138009)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118095
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120074
--- Comment #2 from Andrew Pinski ---
Created attachment 61278
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61278&action=edit
gimple testcase
Compile with -O1 -fgimple.
The reason for the special flags before is because
_5 = _4 & 3;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120074
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120064
Sam James changed:
What|Removed |Added
Target Milestone|--- |15.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120051
Sam James changed:
What|Removed |Added
Summary|codeview ICE/segfault |[15/16 regression] codeview
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120074
Sam James changed:
What|Removed |Added
Summary|ICE on valid code at -O1|[15/16 regression] ICE on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119698
--- Comment #16 from John David Anglin ---
More errors:
RUN c85006e
,.,. C85006E ACATS 2.6 31-02-25 19:41:02
C85006E CHECK THAT A COMPONENT OR SLICE OF A VARIABLE CREATED BY AN
ALLOCATOR CAN BE RENAMED AND HAS THE CORRECT
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120070
Sam James changed:
What|Removed |Added
Last reconfirmed||2025-05-03
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120070
Sam James changed:
What|Removed |Added
Summary|m68k-linux-gnu-gcc -Os ICE |[15/16 regression]
|segfa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21113
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120077
Sam James changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120077
Sam James changed:
What|Removed |Added
CC||lekernel at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120077
Bug ID: 120077
Summary: Switch lm32 to LRA
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: internal-improvement
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120076
Bug ID: 120076
Summary: statement expression allows bypassing own initializer
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: accepts-invalid, stmt-expr
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
pietro changed:
What|Removed |Added
CC||pietro at gcc dot gnu.org
--- Comment #446 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120075
--- Comment #1 from Adam Sampson ---
Created attachment 61277
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61277&action=edit
Non-minimised example
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120075
Bug ID: 120075
Summary: -Wuninitialized warning with internal "SR" variable
name, compiling hb-subset-plan-layout.cc
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
ion 16.0.0 20250502 (experimental) (GCC)
[639] %
[639] % gcctk -O1 small.c; ./a.out
0
[640] % gcctk -O1 -fno-tree-copy-prop -fno-tree-forwprop -fno-tree-ccp small.c
during GIMPLE pass: ifcombine
small.c: In function ‘main’:
small.c:5:5: internal compiler error: in decompose, at wide-int.h:1049
5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120073
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120073
Bug ID: 120073
Summary: __arm_sc_* functions are not included
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: aarch64-sme
Severity: normal
Priority: P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120072
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120072
Sam James changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120072
--- Comment #1 from Sam James ---
I was sure we had another request for this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120072
Bug ID: 120072
Summary: New attribute alloc_variant_zeroed which can be used
for alloc+memset->calloc optimization
Product: gcc
Version: 16.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
--- Comment #5 from Jan Hubicka ---
>
> I think I copied the wrong URLS :).
>
>
> https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=589.507.0
> https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=583.507.0
It would be nice to bis
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120071
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120071
Bug ID: 120071
Summary: Add builtin to get the current PC/instruction counter
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
--- Comment #4 from Andrew Pinski ---
(In reply to Jan Hubicka from comment #3)
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
> >
> > --- Comment #2 from Andrew Pinski ---
> > (In reply to Andrew Pinski from comment #1)
> > > It also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049
--- Comment #8 from kargls at comcast dot net ---
(In reply to Jerry DeLisle from comment #7)
> That is exactly the patch I was testing Steve.
I assume that you've found that you'll need to
deal with both c_ptr_1 and c_ptr_2. With the
short-cir
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
--- Comment #3 from Jan Hubicka ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
>
> --- Comment #2 from Andrew Pinski ---
> (In reply to Andrew Pinski from comment #1)
> > It also happens on aarch64:
> > PGO+LTO:
> > https://lnt.open
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120070
Bug ID: 120070
Summary: m68k-linux-gnu-gcc -Os ICE segfault compiling
xfs_trans_ail.c
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120059
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120059
--- Comment #12 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:dba5d112691a3e10b722468d94fffeda0fdbb818
commit r16-365-gdba5d112691a3e10b722468d94fffeda0fdbb818
Author: Andrew Pinski
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #44 from Eric Botcazou ---
> Right, sorry, I should clarify—I can see what the *actual* effect of
> -mstackrealign / __force_align_arg_pointer__ is. I'm confused at what its
> *intended* effect is. "Align to 16 bytes, but only if we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049
--- Comment #7 from Jerry DeLisle ---
That is exactly the patch I was testing Steve.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049
kargls at comcast dot net changed:
What|Removed |Added
CC||kargls at comcast dot net
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
Sam James changed:
What|Removed |Added
Known to work||16.0
Target Milestone|12.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #43 from Zeb Figura ---
Right, sorry, I should clarify—I can see what the *actual* effect of
-mstackrealign / __force_align_arg_pointer__ is. I'm confused at what its
*intended* effect is. "Align to 16 bytes, but only if we need 16-b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
Zeb Figura changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120048
--- Comment #9 from Andrew Macleod ---
Created attachment 61274
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61274&action=edit
potential patch
(In reply to Andrew Macleod from comment #8)
>
> Another option is to add a type to UNDEFIN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> It also happens on aarch64:
> PGO+LTO:
> https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=792.507.0
> PGO:
> https://lnt.opensuse.org/db_default/v4/SPEC/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
Andrew Pinski changed:
What|Removed |Added
Component|target |tree-optimization
Summary|Ye
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120069
Bug ID: 120069
Summary: Yes another imagick -march=native -flto -Ofast + PGO
regression between
g:1c0cbc1b300e08df5ebfce00a7195890d78f2064 and
g:55b01e17c793688a28
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120057
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120057
--- Comment #7 from GCC Commits ---
The releases/gcc-15 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:14c2a12748eea0eef714a125cb1a6c834fd60560
commit r15-9615-g14c2a12748eea0eef714a125cb1a6c834fd60560
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120057
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:e81f2f4855876c5d85ab9870c5a150ee1a59ee73
commit r16-364-ge81f2f4855876c5d85ab9870c5a150ee1a59ee73
Author: Jakub Jelinek
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120065
--- Comment #3 from Jan Hubicka ---
while (n > 0 && a)
;
This is an odd loop which loops iterates 0 times or infinitely many times.
We do not pattern match that at profile-estimate time (since such code is kind
of useless) and we guess i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119698
John David Anglin changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #4)
> $ gfc -c test.f90
> f951: internal compiler error: gfc_typename(): Undefined type
> 0x694bce diagnostic_report_diagnostic(diagnostic_context*, diagn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
--- Comment #7 from Andrew Pinski ---
(In reply to guido2022 from comment #6)
> The issue is only triggered by using the differential patch and not the
> tarball or git.
Right, the diff is only there for folks to look at and not really use. the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
--- Comment #6 from guido2022 at trentalancia dot com ---
The issue is only triggered by using the differential patch and not the tarball
or git.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
guido2022 at trentalancia dot com changed:
What|Removed |Added
Status|WAITING |RESOLVED
Res
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120067
--- Comment #2 from rdapp.gcc at gmail dot com ---
> This is reduced from 525.x264_r's 4th hottest block:
> https://godbolt.org/z/KdWv1er6f
>
> AArch64 assembly is clean and efficient (35 insns) while RISC-V's is long and
> messy (114 insns).
>
>
This is reduced from 525.x264_r's 4th hottest block:
https://godbolt.org/z/KdWv1er6f
AArch64 assembly is clean and efficient (35 insns) while RISC-V's is long and
messy (114 insns).
The most obvious issue is that it keeps spilling and reloading the same data
from the stack. Also I do not underst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
--- Comment #4 from Andrew Pinski ---
Also can you provide what target are you building for and on?
The exact configure command line?
Did you extract the tar ball not with GNU tar (which is required)?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120067
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
CC||ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049
--- Comment #4 from Jerry DeLisle ---
Vincent was able to reduce this further. Two files, gtk_sup.f90 and test.f90.
$ cat gtk_sup.f90
module gtk_sup
use, intrinsic :: iso_c_binding
end module gtk_sup
$ cat test.f90
program tests_gtk_sup
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> it is executable in git:
> [apinski@xeond2 gcc]$ ls -latr contrib/relpath.sh
> -rwxr-xr-x. 1 apinski apinski 1487 Apr 16 14:32 contrib/relpath.sh
https://gcc.gn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119632
--- Comment #5 from Simon Sobisch ---
@Bob, what do you think of committing that patch as it waits on one of the
COBOL maintainers (and later or work on supporting that - at least as
"ignored")?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
Andrew Pinski changed:
What|Removed |Added
Component|libstdc++ |bootstrap
--- Comment #1 from Andrew Pi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120068
Bug ID: 120068
Summary: The new contrib/relpath.sh script should be made
executable otherwise the build fails
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118100
--- Comment #2 from mcccs at gmx dot com ---
I meant spike --isa=rv64gcv_zvfh pk a.out
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117023
--- Comment #11 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:1e27e9a3184c948b499a21ff20181611514ed720
commit r16-363-g1e27e9a3184c948b499a21ff20181611514ed720
Author: Jakub Jelinek
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120059
Joseph S. Myers changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120067
Bug ID: 120067
Summary: RISC-V: x264 sub4x4_dct high icount
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120061
--- Comment #3 from Jakub Jelinek ---
gcc 14 and earlier uses 32-bit location_t while 15+ 64-bit location_t, so guess
that makes significant difference here, one needs far fewer lines (or
columns/ranges etc.) to reach the limit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120059
--- Comment #10 from Andrew Pinski ---
(In reply to Pengfei Li from comment #9)
> Thanks Andrew for the quick fix. I've bootstrapped and regression tested the
> fix on x86_64 and AArch64.
>
> Apologies for introducing the issue (I'm new to GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119364
--- Comment #24 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:c77d04506e6abdc45969d0ff146204be7485244a
commit r16-362-gc77d04506e6abdc45969d0ff146204be7485244a
Author: Jakub Jelinek
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119364
--- Comment #23 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:4704b94fc76b51e79e6fcf63344f70da4d89d75c
commit r16-361-g4704b94fc76b51e79e6fcf63344f70da4d89d75c
Author: Jakub Jelinek
Date: F
> Sorry again if I included the wrong information, or formatted the email
> wrong or anything like that. It's my first time using a gnu mailing list.
Instructions are at: https://gcc.gnu.org/bugs/, see "Where to post it".
--
Eric Botcazou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120064
Andrew Pinski changed:
What|Removed |Added
Summary|doc: -f[no-]ext-dce not |[15/16 Regression]
|d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120065
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119948
--- Comment #18 from kargls at comcast dot net ---
On 5/2/25 01:06, pault at gcc dot gnu.org wrote:
> I got to thinking for once. I think that your change to primary.cc has cast
> the
> net a bit too wide and risks turning other kinds of interf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120065
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119966
--- Comment #7 from Dimitar Dimitrov ---
Thank you Andrew and Richard for the detailed analysis.
I tried the following change. It gave a few ICE regressions for x86_64, which I
have not yet investigated. The patch fixed most but not all ICE re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118100
mcccs at gmx dot com changed:
What|Removed |Added
CC||mcccs at gmx dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120051
Iouri Kharon changed:
What|Removed |Added
CC||bc-info at styx dot cabel.net
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120066
--- Comment #2 from Andrew Pinski ---
Fixed this morning.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120055
Andrew Pinski changed:
What|Removed |Added
CC||danglin at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120066
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120066
Bug ID: 120066
Summary: FAIL: gcc.c-torture/compile/pr51694.c -O0 (internal
compiler error: Segmentation fault)
Product: gcc
Version: 16.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120048
--- Comment #8 from Andrew Macleod ---
IKt seems the root problem is that the ipa_vr class doesn't support UNDEFINED
ranges, and in this case it has a range but when the bitmask is explicitly
applied, we recognize that the range is actualyl UNDE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120065
Bug ID: 120065
Summary: [14/15/16 Regression] profile info corrupted by dom2
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119929
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119900
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:c85148d036d17295bb2560e10020c924c83a5d13
commit r16-358-gc85148d036d17295bb2560e10020c924c83a5d13
Author: Jan Hubicka
Date: Fri Ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115207
--- Comment #4 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:2d7a0d38e2f8e281ab2269cfe6c048410fa3c886
commit r16-357-g2d7a0d38e2f8e281ab2269cfe6c048410fa3c886
Author: Jason Merrill
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120050
Xi Ruoyao changed:
What|Removed |Added
Keywords|needs-bisection |needs-reduction
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120056
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120064
Bug ID: 120064
Summary: doc: -f[no-]ext-dce not documented
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120061
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98753
--- Comment #19 from Adam Mitz ---
Bison users may insert arbitrary code (like a #pragma) in the input file which
is copied to the output. As an example, this is used to silence GCC's warning
here
https://github.com/DOCGroup/ACE_TAO/blob/e3b027b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120063
--- Comment #1 from ensadc at mailnesia dot com ---
AFAIK this can be fixed by adding `case DK_FATAL` to `maybe_get_sarif_level` in
`diagnostic-format-sarif.cc`.
diff --git a/gcc/diagnostic-format-sarif.cc b/gcc/diagnostic-format-sarif.cc
index
1 - 100 of 141 matches
Mail list logo
