https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108532
--- Comment #1 from Richard Biener ---
With streamable flags produced by the object files I wonder if it makes sense
to drop linker target arguments on the floor? (they'd be effectively ignored
anyway in some way)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108528
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
--- Comment #11 from rguenther at suse dot de ---
On Tue, 24 Jan 2023, qing.zhao at oracle dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
>
> --- Comment #10 from Qing Zhao ---
> > --- Comment #9 from Richard Biener ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531
--- Comment #4 from Sam James ---
LLVM side: https://github.com/llvm/llvm-project/issues/60269
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105807
--- Comment #4 from Andrew Benson ---
A possibly related case:
module tm
type :: st
end type st
type :: resourceManager
class (*), pointer :: resource => null()
integer , pointer :: counter => null()
end type resourceMan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108218
Jason Merrill changed:
What|Removed |Added
Status|RESOLVED|SUSPENDED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108218
Jason Merrill changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108534
--- Comment #2 from Ian Lance Taylor ---
Yes, it's a relative path, such as
#line 1 "cgo-gcc-prolog"
These are dummy but informative line markers used to separate generated code
from user-written code, so that compiler error messages repor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108388
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
--- Comment #3 from CVS Commits ---
The master branch has been updated by Siddhesh Poyarekar
:
https://gcc.gnu.org/g:b851ee9fdf0f3023635f0cb1f7c607b2d6801053
commit r13-5341-gb851ee9fdf0f3023635f0cb1f7c607b2d6801053
Author: Siddhesh Poyarekar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108534
--- Comment #1 from Andrew Pinski ---
const char *remapped = remap_debug_filename (xloc.file);
if (ob->emit_pwd && remapped && !IS_ABSOLUTE_PATH (remapped))
{
stream_pwd = true;
ob->emi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
--- Comment #6 from Jonathan Wakely ---
Should be fixed, if this works on that machine:
$ grep ^DEFAULT_TIMEZONE= /etc/sysconfig/clock
DEFAULT_TIMEZONE="UTC"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:e00d5cafbe1a2ecc57eec921ff0b7dd41344
commit r13-5339-ge00d5cafbe1a2ecc57eec921ff0b7dd41344
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102301
--- Comment #12 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:33ed11085837e9492c6ed512931f5b6375c68ee7
commit r13-5338-g33ed11085837e9492c6ed512931f5b6375c68ee7
Author: Jonathan Wakely
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108533
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108533
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:aba6416e95ab4138a0ecab0fd51e7e9329d74a45
commit r13-5337-gaba6416e95ab4138a0ecab0fd51e7e9329d74a45
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107329
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:aba6416e95ab4138a0ecab0fd51e7e9329d74a45
commit r13-5337-gaba6416e95ab4138a0ecab0fd51e7e9329d74a45
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108533
--- Comment #1 from Andrew Pinski ---
I think the first argument of operator new should be __SIZE_TYPE__ instead of
"unsigned long" likewise for the second argument of operator delete.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108535
Bug ID: 108535
Summary: RFE: analyzer to allow ifdef inclusion/exclusion like
cppcheck -D/-U
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108534
Bug ID: 108534
Summary: LTO streamer does not remap source directory
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108533
Bug ID: 108533
Summary: [13 regression] new test g++.dg/init/new51.C in
r13-5318-g049a5290907511 fails for 32 bits
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107484
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108526
Jason Merrill changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108504
Jason Merrill changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108526
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:39ade88fa1632c659c5c4ed065fa2b62d16a8670
commit r13-5334-g39ade88fa1632c659c5c4ed065fa2b62d16a8670
Author: Jason Merrill
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108504
--- Comment #2 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:327d45c57ebd2655a7599df0f01b8b5e2f82eda7
commit r13-5335-g327d45c57ebd2655a7599df0f01b8b5e2f82eda7
Author: Jason Merrill
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |13.0
Assignee|unas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108532
Bug ID: 108532
Summary: march used on the object but mcpu conflicts still
produces an warning with LTO
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108504
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
--- Comment #2 from seurer at gcc dot gnu.org ---
Yes it is a regular file.
With the previous commit it wasn't UNSUPPORTED and worked just fine:
g:ff6c7617102df365918402c6ccc8e497c47dbe60, r13-5167-gff6c7617102df3
make -k check RUNTESTFLAGS="c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108518
--- Comment #2 from Andrew Pinski ---
In similar fashion memcpy/memset with a size argument of 0 passed, they have to
be a non-null pointer.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108518
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85741
Bug 85741 depends on bug 108518, which changed state.
Bug 108518 Summary: Format-overflow warning using `*.s` directive with null but
zero-length string
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108518
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108388
--- Comment #2 from CVS Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:265a749f290f7c6adc9a3aaa9c585b498a8a38ea
commit r13-5332-g265a749f290f7c6adc9a3aaa9c585b498a8a38ea
Author: Vladimir N. Makarov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531
--- Comment #3 from Keith Thompson ---
In the latest C2X draft,
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3054.pdf
Annex G still requires imaginary number support for any implementation
that defines __STDC_IEC_60559_COMPLEX__ or __STDC_I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
--- Comment #5 from Steve Kargl ---
On Tue, Jan 24, 2023 at 08:51:03PM +, anlauf at gcc dot gnu.org wrote:
> --- Comment #4 from anlauf at gcc dot gnu.org ---
> The patch in comment#2 regtests cleanly.
>
> I can package it and submit if you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
--- Comment #4 from anlauf at gcc dot gnu.org ---
The patch in comment#2 regtests cleanly.
I can package it and submit if you agree.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
--- Comment #2 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:6c96382eed96a9285611f2e3e2e59557094172b8
commit r13-5331-g6c96382eed96a9285611f2e3e2e59557094172b8
Author: Harald Anlauf
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108521
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108521
Andrew Pinski changed:
What|Removed |Added
URL|https://gcc.gnu.org/git?p=g |
|cc.git;a=blob;f=gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108528
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=108526
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
--- Comment #1 from Jonathan Wakely ---
I think those tests were being skipped as UNSUPPORTED before that commit. The
point of the commit was to enable these features on systems that don't provide
a tzdata.zi file.
What does 'ls -l /etc/localt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531
--- Comment #2 from Andrew Pinski ---
C2x changes this ... (so does TS 18661-1 ) so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531
--- Comment #1 from Keith Thompson ---
After I submitted this, I found that this is probably a duplicate of:
https://sourceware.org/bugzilla/show_bug.cgi?id=15720
(I disagree with the resolution of that bug report.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7263
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |4.8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531
Bug ID: 108531
Summary: Imaginary types are not supported, violating ISO C
Annex G
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Summary|-O1 -fcode-hois
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
Bug ID: 108530
Summary: [13 regression] std/time/tzdb/1.cc fails after
r13-5168-g559993b85744ae
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
David Binderman changed:
What|Removed |Added
CC||rguenther at suse dot de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #2)
> This fixes all testcases. These two helper functions can indicate
> a problem occurs, so instead of asserting on (a->ts.type != BT_INTEGER)
> return the CMP_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108528
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108528
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #7 from David Binderman ---
Git range now seems to be g:4d08c674b0114622 .. g:36cabc257dfb7dd4
which is 8 commits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-01-24
Statu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #6 from David Binderman ---
Git range now seems to be g:4d08c674b0114622 .. g:b2aa75ded65f8c02
which is a range of 33 commits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108526
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
--- Comment #2 from Jakub Jelinek -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
--- Comment #2 from Jakub Jelinek ---
Ah, actually
off = size_binop (PLUS_EXPR, DECL_FIELD_OFFSET (t),
size_int (tree_to_uhwi (DECL_FIELD_BIT_OFFSET (t))
/ BITS_PER_UNIT));
So:
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #5 from David Binderman ---
Current range seems to be g:4d08c674b0114622 .. g:400d9fc1f0433611
which is 133 commits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108526
Andrew Pinski changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Target Miles
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108515
Richard Earnshaw changed:
What|Removed |Added
Resolution|FIXED |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108525
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #4 from David Binderman ---
Seems to run fine in about 0.1 seconds with g:4d08c674b0114622,
dated 20221129.
That seems to be about 533 commits.
I'll have a go at a git bisect.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108525
--- Comment #3 from Andrew Pinski ---
Most likely the ICE started when static operator() support (for C++23) came in
via r13-2892-g303976a6076f28 .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
Bug ID: 108529
Summary: [10/11/12/13 Regression] ICE in
transformational_result, at fortran/simplify.cc:478
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Seve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108525
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108525
--- Comment #2 from Jakub Jelinek ---
Started with my r13-2892-g303976a6076f2839354702fd2caa049fa7cbbdc2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108528
Bug ID: 108528
Summary: [13 Regression] ICE in gfc_compare_array_spec(): Array
spec clobbered
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108525
Andrew Pinski changed:
What|Removed |Added
Keywords|ice-on-invalid-code |ABI, ice-on-valid-code
Ever confirm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
Bug ID: 108527
Summary: [13 Regression] ICE in compare_bound_int(): Bad
expression
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532
--- Comment #7 from Marek Polacek ---
Sadly, I'm pretty certain it won't get fixed by P2718R0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108526
Bug ID: 108526
Summary: [13 Regression] ICE in start_preparsed_function, at
cp/decl.cc:17281
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108525
Bug ID: 108525
Summary: [13 Regression] ICE in write_method_parms, at
cp/mangle.cc:2864
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108498
--- Comment #24 from Jakub Jelinek ---
(In reply to Eric Botcazou from comment #23)
> > The C/C++ FEs since r9-6625-gbec1da64aec26a490 turn some array initializers
> > into strings.
>
> Ouch. I'm not sure that's worthwhile if the arrays are no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532
--- Comment #6 from Jakub Jelinek ---
(In reply to Marek Polacek from comment #5)
> It's tricky. I've seen unfixable problems with range-based for loops, for
> instance.
Shouldn't those be fixed once P2718R0 is implemented (at least for C++23)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #3 from David Binderman ---
Problem seems to start sometime before git hash g:9b111debbfb79a0a,
dated 20221229.
I'll try a build of a month earlier.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532
--- Comment #5 from Marek Polacek ---
(In reply to Jakub Jelinek from comment #4)
> Yeah, without analyzing what the function call (constructor in this case)
> actually does
> hard to say whether the warning is ok or not.
> Maybe some heuristics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108498
--- Comment #23 from Eric Botcazou ---
> The C/C++ FEs since r9-6625-gbec1da64aec26a490 turn some array initializers
> into strings.
Ouch. I'm not sure that's worthwhile if the arrays are not byte-aligned.
> Anyway, I wonder if for GCC 14 we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #2 from David Binderman ---
Doesn't complete in 1200 seconds.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108524
Bug ID: 108524
Summary: -Wanalyzer-infinite-recursion false positives seen in
qemu's JSON parser
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108498
--- Comment #22 from Jakub Jelinek ---
The C/C++ FEs since r9-6625-gbec1da64aec26a490 turn some array initializers
into strings.
Anyway, I wonder if for GCC 14 we couldn't just treat STRING_CST the same as
INTEGER_CST during the merging into gr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108512
--- Comment #2 from Tobias Burnus ---
Patch submission:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610531.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523
--- Comment #1 from David Binderman ---
Also won't run to completion with a ulimit of 750 seconds.
Trying 1200 seconds.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #4 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:c1093923733a1072a237f112e3239b5ebd88eadd
commit r13-5327-gc1093923733a1072a237f112e3239b5ebd88eadd
Author: Andre Vieira
compile normally:
$ (ulimit -t 300; time ../results.20230124.release/bin/gcc -c -w -O1
-fno-var-tracking bug875.c)
real0m0.133s
user0m0.095s
sys 0m0.013s
Add in -fcode-hoisting and it seems to take a lot longer:
$ (ulimit -t 300; time ../results.20230124.release/bin/gcc -c -w -O1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
Siddhesh Poyarekar changed:
What|Removed |Added
See Also||https://bugzilla.redhat.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108522
Bug ID: 108522
Summary: [Regression 12/13] ICE in tree-object-size when struct
has VLA
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108498
--- Comment #21 from Eric Botcazou ---
> That said, I think especially for backports to 11/12 and perhaps even for 13
> the easiest will be the second option, clear string_merging on non-aligned
> start/width.
>
> Eric, your thoughts on this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108521
Brian W. Inglis changed:
What|Removed |Added
CC||Brian.Inglis at SystematicSw
dot a
1 - 100 of 198 matches
Mail list logo
