https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116283
Bug ID: 116283
Summary: [15 Regression] RISC-V rv64id_zbs ICE: unrecognizable
insn
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115062
--- Comment #2 from Nathaniel Shead ---
This minimal patch fixes the (reduced) issue:
diff --git a/gcc/cp/class.cc b/gcc/cp/class.cc
index 718601756dd..81429f3a73b 100644
--- a/gcc/cp/class.cc
+++ b/gcc/cp/class.cc
@@ -2312,6 +2312,7 @@ fixup_t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #145 from John Paul Adrian Glaubitz ---
(In reply to Kazumoto Kojima from comment #144)
> It seems that all ICEs in the log in c#142 are the pcrel call issues
> described in c#129 which could be avoided with the patch 58831.
OK, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116275
--- Comment #3 from Sam James ---
(In reply to Sam James from comment #2)
(Make SymbolAddressOrErr a parameter for it to be well-defined.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 115801, which changed state.
Bug 115801 Summary: [modules] segfault instantiating a template with a
templated friend declaration referring to an unexported template using a
qualified name
https://gcc.gnu.org/bugzilla/s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115801
Nathaniel Shead changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 114950, which changed state.
Bug 114950 Summary: [modules] ICE in binding_cmp when merging friend functions
in partitions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114950
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114950
Nathaniel Shead changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |nshead at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115801
--- Comment #5 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:79209273663672ff05663554741fd2558b4aac99
commit r15-2808-g79209273663672ff05663554741fd2558b4aac99
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114950
--- Comment #1 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:c592310d5275e09977504c136419686bd2277af0
commit r15-2807-gc592310d5275e09977504c136419686bd2277af0
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116252
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116282
Bug ID: 116282
Summary: [15 Regression] RISC-V rv64id_zba_zbkb ICE: could not
split insn
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116191
Levi Morrison changed:
What|Removed |Added
CC||morrison.levi at gmail dot com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116281
--- Comment #2 from Halalaluyafail3 ---
(In reply to Andrew Pinski from comment #1)
> EDG also rejects it:
> ```
> "", line 3: error: expected an identifier
> int y=0?0,0:0;
> ^
> ```
>
>
> Are you sure this is valid code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116281
--- Comment #1 from Andrew Pinski ---
EDG also rejects it:
```
"", line 3: error: expected an identifier
int y=0?0,0:0;
^
```
Are you sure this is valid code and not a bug in clang?
Especially when 3 out of the 4 major fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116281
Bug ID: 116281
Summary: Comma operator used in the middle operand of a
conditional expression is incorrectly rejected in non
static data member initializer
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91940
--- Comment #10 from Jorn Wolfgang Rennecke ---
Even if you add support for V2HI bswap, it won't help vectorization without
support for V4QI vectors and permutations, because vectorizable_bswap won't
recognize the bswap capability of the target a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91940
Jorn Wolfgang Rennecke changed:
What|Removed |Added
CC||amylaar at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
--- Comment #8 from Li Pan ---
(In reply to Li Pan from comment #7)
> The backend take
> rtx xmode_x = gen_lowpart (Xmode, x);
>
> For the incoming op of .SAT_ADD, thus I think we should take lbu instead of
> lb according to the ISA.
During u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
--- Comment #7 from Li Pan ---
The backend take
rtx xmode_x = gen_lowpart (Xmode, x);
For the incoming op of .SAT_ADD, thus I think we should take lbu instead of lb
according to the ISA.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
--- Comment #6 from Li Pan ---
(In reply to Andrew Pinski from comment #4)
> lb a1,0(a5) // load -40
> lui a0,%hi(.LC0)
> lui a4,%hi(c)
> addia5,a1,9 //a5 = -31
> sllia5,a5,48
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
--- Comment #5 from Li Pan ---
Reproduced from both qemu and hardware, let me take a look.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116280
Bug ID: 116280
Summary: [15 Regression] RISC-V: expected mode RVVMF8QI for
operand 2 of insn pred_vwsllrvvmf4hi but got mode
RVVMF2SI
Product: gcc
Version: 15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
--- Comment #4 from Andrew Pinski ---
lb a1,0(a5) // load -40
lui a0,%hi(.LC0)
lui a4,%hi(c)
addia5,a1,9 //a5 = -31
sllia5,a5,48
srlia5,a5,48 // a5 = -31
sltua
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
--- Comment #3 from Li Pan ---
(In reply to Kito Cheng from comment #2)
> Hi Pan, could you take a look to see if it related to SAT_ADD?
Ack, thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116279
Bug ID: 116279
Summary: Branch coverage measure is reported in inconsistent
ways for comma operators
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
--- Comment #1 from Andrew Pinski ---
This might be a SAT_ADD issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116275
--- Comment #2 from Sam James ---
Thank you Roger!
Reduced:
```
struct SymbolDesc push_back(SymbolDesc);
struct SymbolDesc {
long long ELFLocalSymIdx;
};
struct Expected {
long long &operator*();
};
void SymbolizableObjectFileaddSymbol() {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
Bug ID: 116278
Summary: [15] RISC-V: Miscompile at -O2 -fwrapv
-fno-strict-aliasing
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116277
--- Comment #4 from Andrew Pinski ---
(In reply to Frank Heckenbach from comment #3)
> When 63446 was reported, gcc didn't have -Werror=dangling-reference, so a
> false positive was perhaps better than no warning in this case back then.
> Now it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115062
Nathaniel Shead changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116277
--- Comment #3 from Frank Heckenbach ---
When 63446 was reported, gcc didn't have -Werror=dangling-reference, so a false
positive was perhaps better than no warning in this case back then. Now it has
the proper warning for this case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63446
Andrew Pinski changed:
What|Removed |Added
CC||f.heckenb...@fh-soft.de
--- Comment #10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116277
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116277
--- Comment #1 from Andrew Pinski ---
I think this is a dup.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116277
Bug ID: 116277
Summary: "may be used uninitialized
[-Werror=maybe-uninitialized]" instead of
-Werror=dangling-reference
Product: gcc
Version: 14.1.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116276
--- Comment #2 from Patrick Palka ---
In C++20 mode it works because of the default ctor guide
[over.match.class.deduct]/1.2: "If C is not defined or does not declare any
constructors, an additional function template derived as above from a
hypo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #144 from Kazumoto Kojima ---
It seems that all ICEs in the log in c#142 are the pcrel call issues described
in c#129 which could be avoided with the patch 58831.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #65 from Kees Cook ---
(In reply to Alejandro Colomar from comment #64)
> How about having two macros? One that works for non-attributed pointers,
> and other that works for attributed ones. And use the appropriate one for
> each o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116276
Patrick Palka changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #64 from Alejandro Colomar ---
(In reply to Kees Cook from comment #63)
> (In reply to Alejandro Colomar from comment #62)
> > What's the value of returning NULL instead of just failing the compilation
> > with an error?
>
> It's so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #63 from Kees Cook ---
(In reply to Alejandro Colomar from comment #62)
> What's the value of returning NULL instead of just failing the compilation
> with an error?
It's so that the same allocator macros can be used for FAM structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116015
Marek Polacek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116238
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-08-07
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116238
--- Comment #2 from Andrew Pinski ---
Created attachment 58864
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58864&action=edit
Reduced testcase
`-Ofast -msve-vector-bits=128 -march=armv9-a -fno-vect-cost-model `
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116238
--- Comment #1 from Andrew Pinski ---
Created attachment 58863
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58863&action=edit
Just this file with `-Ofast -msve-vector-bits=128 -march=armv9-a`
[apinski@xeond2 t]$ ../xgcc -B.. t2.c -Ofast
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #62 from Alejandro Colomar ---
(In reply to qinzhao from comment #61)
> (In reply to qinzhao from comment #60)
> > I came up with the following draft for the documentation of the new
> > __builtin_get_counted_by, let me know your com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116276
Jason Merrill changed:
What|Removed |Added
Priority|P3 |P2
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116276
Jason Merrill changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116276
Bug ID: 116276
Summary: [14/15 regression] multiple inheritance CTAD
regression with -std=c++23
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116275
Roger Sayle changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116128
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to mjr19 from comment #3)
> It seems that most of these are in-line expanded by gfortran-14.1, at least
> in some cases.
>
> function foo(a,n)
> real(kind(1d0))::a(*),foo
> integer:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112358
--- Comment #8 from Joseph S. Myers ---
If it's a false positive, it's reasonable to work around in glibc using the
libc-diag.h macros (DIAG_PUSH_NEEDS_COMMENT / DIAG_IGNORE_NEEDS_COMMENT /
DIAG_POP_NEEDS_COMMENT) - but that would need an approp
--enable-host-pie --disable-host-bind-now
--enable-default-ssp --disable-fixincludes --with-build-config='bootstrap-O3
bootstrap-lto'
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 15.0.0 20240807 (experimental)
2083389a18d36684a88d9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116237
--- Comment #2 from Sergey Fedorov ---
Thank you, Iain!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112358
--- Comment #7 from Jeffrey A. Law ---
It could well be the case that the threader could transform this code to
eliminate the unexecutable path, but that it wasn't deemed profitable, thus
leaving a path in the IL that will never occur at runtime
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116237
--- Comment #1 from GCC Commits ---
The master branch has been updated by Iain D Sandoe :
https://gcc.gnu.org/g:4cec7bc79db52bae159c3c60a415e2aea48051d8
commit r15-2803-g4cec7bc79db52bae159c3c60a415e2aea48051d8
Author: Iain Sandoe
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112358
--- Comment #6 from John David Anglin ---
This note seems bogus:
In function '_dl_find_object_update':
cc1: note: destination object is likely at address zero
bool
_dl_find_object_update (struct link_map *new_map)
{
/* Copy the newly-loaded
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116271
--- Comment #2 from Jorn Wolfgang Rennecke ---
Created attachment 58861
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58861&action=edit
proposed patch
Does this patch work for you?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #143 from John Paul Adrian Glaubitz ---
The most common failure seems to be "error: unable to generate reloads for" and
it occurs often in routine for integer arithmetic.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #142 from John Paul Adrian Glaubitz ---
(In reply to John Paul Adrian Glaubitz from comment #141)
> (In reply to Oleg Endo from comment #140)
> > Created attachment 58860 [details]
> > testcase for attachment 58831 [details], 58832,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116064
--- Comment #9 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:d1fc9816df81e953308428641685d6ec6d84c9ac
commit r15-2802-gd1fc9816df81e953308428641685d6ec6d84c9ac
Author: Patrick Palka
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96265
--- Comment #8 from GCC Commits ---
The master branch has been updated by Prathamesh Kulkarni
:
https://gcc.gnu.org/g:38900247f3880d6eca2e364a000e5898f8deae64
commit r15-2801-g38900247f3880d6eca2e364a000e5898f8deae64
Author: Prathamesh Kulkarni
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111937
--- Comment #8 from GCC Commits ---
The master branch has been updated by Prathamesh Kulkarni
:
https://gcc.gnu.org/g:38900247f3880d6eca2e364a000e5898f8deae64
commit r15-2801-g38900247f3880d6eca2e364a000e5898f8deae64
Author: Prathamesh Kulkarn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116271
--- Comment #1 from Jorn Wolfgang Rennecke ---
I have overlooked that, in the inner loop of s176, the array index i+m-j-1
turns negativeat for higher iterations of the middle loop for small m.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116219
--- Comment #17 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:165e3e7c3ba884345647c0f1c9a3a57a03383651
commit r15-2800-g165e3e7c3ba884345647c0f1c9a3a57a03383651
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116274
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Target Milestone|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116274
Bug ID: 116274
Summary: x86: poor code generation with 16 byte function
arguments
Product: gcc
Version: 14.2.1
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116273
Bug ID: 116273
Summary: [14/15 regression] RISC-V: gcc.dg/long_branch.c flakey
timeout
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #61 from qinzhao at gcc dot gnu.org ---
(In reply to qinzhao from comment #60)
> I came up with the following draft for the documentation of the new
> __builtin_get_counted_by, let me know your comments and suggestions:
After discuss
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116272
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109126
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94404
Bug 94404 depends on bug 109126, which changed state.
Bug 109126 Summary: [DR2387] Linkage of const-qualified variable template
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109126
What|Removed |Added
---
-13 test.c -O2; ./a.out
1
$
$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=/root/compilers/gcc/gcc-trunk-20240807/bin/gcc
COLLECT_LTO_WRAPPER=/root/compilers/gcc/gcc-trunk-20240807/libexec/gcc/aarch64-unknown-linux-gnu/15.0.0/lto-wrapper
Target: aarch64-unknown-linux-gnu
Configured with: ./configure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109126
--- Comment #4 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:82cd63a63eaa61a4ed5c4029a1869be7446ecb3c
commit r15-2798-g82cd63a63eaa61a4ed5c4029a1869be7446ecb3c
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116258
--- Comment #7 from Andrew Pinski ---
(In reply to Richard Biener from comment #4)
> Fixed on trunk, I do plan to backport.
ok, thanks for the fix, I added 2 aarch64 specific testcases, one for the VLA
vectors since that was not being tested be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116259
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116258
--- Comment #6 from Andrew Pinski ---
*** Bug 116259 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116258
--- Comment #5 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:2c6174402ea315ecf618cfcba741e8cb18bc5282
commit r15-2797-g2c6174402ea315ecf618cfcba741e8cb18bc5282
Author: Andrew Pinski
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116259
--- Comment #1 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:2c6174402ea315ecf618cfcba741e8cb18bc5282
commit r15-2797-g2c6174402ea315ecf618cfcba741e8cb18bc5282
Author: Andrew Pinski
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116166
Mark Wielaard changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116266
--- Comment #2 from Peter Bergner ---
(In reply to Kewen Lin from comment #0)
> I think not having TARGET_P10_VECTOR isn't intentional, as we still allow
> -mno-vsx with -mcpu=power10. We have TARGET_P8_VECTOR and TARGET_P9_VECTOR
> for P8 and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107222
Patrick Palka changed:
What|Removed |Added
CC||jason at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116254
John David Anglin changed:
What|Removed |Added
CC||danglin at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116148
--- Comment #12 from John David Anglin ---
Adding -funsigned-char fixes test. Posted change also fixes test.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116140
Alex Coplan changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |acoplan at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114461
--- Comment #5 from Jakub Jelinek ---
Oh, and I think there is another problem with that paper.
module : private ;
is valid, but the addition of https://eel.is/c++draft/cpp.module#2 stands in a
way,
the pp-tokens in that case don't match pp-modu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #141 from John Paul Adrian Glaubitz ---
(In reply to Oleg Endo from comment #140)
> Created attachment 58860 [details]
> testcase for attachment 58831 [details], 58832, 58833, 58836
> (...)
> The issue goes away after applying att
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116064
--- Comment #8 from Patrick Palka ---
One can now use -fpermissive or -Wno-error=template-body to compile TUs
containing errors inside uninstantiated templates.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116271
Bug ID: 116271
Summary: [15 regression] gcc.dg/vect/tsvc/vect-tsvc-s176.c
fails after r15-2777-g8fac69a2dbff98
Product: gcc
Version: 15.0
Status: UNCONFIRMED
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116261
Sam James changed:
What|Removed |Added
Target|riscv |riscv,powerpc64-linux-gnu,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116261
Sam James changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
--- Comment #1 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116270
Sam James changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102061
--- Comment #6 from Peter Damianov ---
I confirmed this is the case. Compiling the example from the testcase
independent-cloneids-1.c confirms that lhd_decl_printable_name is also used for
-fdump-rtl-final, my patch results in:
;; Function bar (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116270
Bug ID: 116270
Summary: [15 regression] erratic failures (time outs) of
gfortran.dg/sizeof_6.f90
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #60 from qinzhao at gcc dot gnu.org ---
I came up with the following draft for the documentation of the new
__builtin_get_counted_by, let me know your comments and suggestions:
Builtin-in Function: type __builtin_get_counted_by (ptr)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #140 from Oleg Endo ---
Created attachment 58860
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58860&action=edit
testcase for attachment 58831, 58832, 58833, 58836
The attached test case, when compiled with 'sh-elf-gcc -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116268
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107087
Ted Lyngmo changed:
What|Removed |Added
CC||ted at lyncon dot se
--- Comment #20 from
1 - 100 of 149 matches
Mail list logo
