https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108797
--- Comment #2 from Holger Kaelberer ---
I expected that. Just for reference: Where can I find release-planning for
specific releases/xxx branches of gcc?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108797
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108797
Bug ID: 108797
Summary: libstdc++: Inconsistent noexcept-specific for valarray
begin/end
Product: gcc
Version: 9.5.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108738
--- Comment #6 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:e1dfac7e71056e879f101fef1c5ecb8ff6be1a1f
commit r13-5995-ge1dfac7e71056e879f101fef1c5ecb8ff6be1a1f
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108738
--- Comment #5 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:ec23e9e25eb64bb066dc408fd498861b8587bec8
commit r13-5994-gec23e9e25eb64bb066dc408fd498861b8587bec8
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107096
--- Comment #12 from rguenther at suse dot de ---
On Wed, 15 Feb 2023, crazylht at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107096
>
> --- Comment #11 from Hongtao.liu ---
>
> >
> > There's no other way to do N bi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107096
--- Comment #11 from Hongtao.liu ---
>
> There's no other way to do N bit to two N/2 bit hi/lo (un)packing
> (there's a 2x N/2 bit -> N bit operation, for whatever reason).
> There's also no way to transform the d rgroup mask into the
> f rgro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107096
--- Comment #10 from Hongtao.liu ---
>
> There's no other way to do N bit to two N/2 bit hi/lo (un)packing
> (there's a 2x N/2 bit -> N bit operation, for whatever reason).
> There's also no way to transform the d rgroup mask into the
> f rgro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69585
--- Comment #6 from Andrew Pinski ---
I see this only changed the C++ front-end. sudo just ran into a similar issue
for the C front-end, see PR 108796.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
Andrew Pinski changed:
What|Removed |Added
Summary|GCC 13 accepts [[noreturn]] |Can't intermix C2x and GNU
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
Andrew Pinski changed:
What|Removed |Added
Resolution|DUPLICATE |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101682
Sam James changed:
What|Removed |Added
CC||sam at gentoo dot org
--- Comment #7 from S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
Sam James changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #3 from Sam James --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
--- Comment #2 from Sam James ---
Sorry, for completeness, I meant to include:
```
$ gcc-12 -O2 /tmp/foo.c # ditto with -std=c89
/tmp/foo.c:3:1: warning: 'noreturn' attribute ignored [-Wattributes]
3 | [[noreturn]] void foo(void) {
| ^
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
Sam James changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
Bug ID: 108796
Summary: GCC 13 accepts [[noreturn]] attribute without -std=c2x
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108699
--- Comment #3 from Kewen Lin ---
One more test case fail with abort on both LE & BE (with -Ofast -mcpu=power9):
#define N 16
unsigned long long vals[N];
unsigned int res[N];
unsigned int expects[N] = {0, 1, 1, 1, 1, 1, 1, 0, 0, 0, 0, 0,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106675
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Summary|[10/11/12/13 R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106675
--- Comment #6 from CVS Commits ---
The releases/gcc-11 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:53512f0055186d5556e9859c1f8beb25d2d28530
commit r11-10525-g53512f0055186d5556e9859c1f8beb25d2d28530
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106675
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:1721d85708116a1edbe5ba30f055d47e6c1e29b6
commit r12-9174-g1721d85708116a1edbe5ba30f055d47e6c1e29b6
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106675
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:cce62625025380c2ea2a220deb10f8f355f83abf
commit r13-5990-gcce62625025380c2ea2a220deb10f8f355f83abf
Author: Marek Polacek
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108261
Gaius Mulley changed:
What|Removed |Added
Status|NEW |WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108261
--- Comment #21 from Gaius Mulley ---
For clarity the "RTentity uninitialized Storage module" error has disappeared.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108261
Gaius Mulley changed:
What|Removed |Added
CC||gaius at gcc dot gnu.org
--- Comment #20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
--- Comment #10 from Marek Polacek ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Marek Polacek from comment #7)
> > I know you can't jump into a statement expression but that's not what's
> > happening here. The kernel uses thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
--- Comment #8 from Andrew Pinski ---
(In reply to Marek Polacek from comment #7)
> I know you can't jump into a statement expression but that's not what's
> happening here. The kernel uses this trick to get the current address for
> error mess
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108790
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Faust :
https://gcc.gnu.org/g:c348a717213b03c6661878934f197f4d261f0e56
commit r13-5989-gc348a717213b03c6661878934f197f4d261f0e56
Author: David Faust
Date: Tue F
On Tue, Feb 14, 2023 at 2:14 PM Owen Cook via Gcc-bugs
wrote:
>
> Adding white space/newlines outside the function also affect the length of
> assembly.
Note -march=native is dependent on the machine which is being used.
IIRC godbolt uses a few different machines and that means the answer
which -
Adding white space/newlines outside the function also affect the length of
assembly.
On Tue, Feb 14, 2023 at 5:09 PM Owen Cook wrote:
> Within "unrollOptimizations.c" compiled on a Ryzen 5 2600 using x86-64 gcc
> 12.2 "-O2 -march=native" gives vastly different assembler results given
> some scop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
--- Comment #7 from Marek Polacek ---
I know you can't jump into a statement expression but that's not what's
happening here. The kernel uses this trick to get the current address for
error messages:
#define __this_address ({ __label__ __here;
Within "unrollOptimizations.c" compiled on a Ryzen 5 2600 using x86-64 gcc
12.2 "-O2 -march=native" gives vastly different assembler results given
some scope things I have found. If the for loop iterator name is both int i
in each loop, gcc seemingly spreads arrayA and arrayB into one single XMM
re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
--- Comment #6 from Andrew Pinski ---
On the statement expression part, it is documented that jumping into statement
expression is not allowed too:
https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Statement-Exprs.html#Statement-Exprs
>Jumping into
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
--- Comment #5 from Andrew Pinski ---
(In reply to Marek Polacek from comment #3)
> I don't think we should be warning here at all and I have a patch to that
> effect.
I also disagree with the saying we should not be warning here. Address to
la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
--- Comment #4 from Andrew Pinski ---
(In reply to Marek Polacek from comment #3)
> This came up in kernel: https://bugzilla.kernel.org/show_bug.cgi?id=215851
> which I've reduced to
>
> void
> foo (void **failaddr)
> {
> *failaddr = ({ __la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106080
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108795
Marek Polacek changed:
What|Removed |Added
Target Milestone|--- |10.5
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19987
Bug 19987 depends on bug 96921, which changed state.
Bug 96921 Summary: Failure to optimize combined boolean not patterns
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96921
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108354
Bug 108354 depends on bug 96921, which changed state.
Bug 96921 Summary: Failure to optimize combined boolean not patterns
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96921
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96921
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108355
--- Comment #4 from Andrew Pinski ---
(In reply to CVS Commits from comment #3)
> The trunk branch has been updated by Andrew Pinski :
Sorry I forgot to fix the commit message for the corrected bug #.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108354
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108355
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:a42ed1d9181d21d5cb02f131f641c0cf375eca9d
commit r13-5988-ga42ed1d9181d21d5cb02f131f641c0cf375eca9d
Author: Andrew Pinski
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96921
--- Comment #10 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:a42ed1d9181d21d5cb02f131f641c0cf375eca9d
commit r13-5988-ga42ed1d9181d21d5cb02f131f641c0cf375eca9d
Author: Andrew Pinski
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107972
--- Comment #5 from Andrew Macleod ---
(In reply to Jakub Jelinek from comment #3)
> The backwards propagation fixed, but neither:
<...>
> avoids the 4.2e+1 cases in the output, because in neither case we properly
> determine the ranges of res (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90458
--- Comment #8 from nightstrike ---
FYI, this is the same as the failure in gcc/testsuite/gcc.dg/stack-check-16.c:
(running this under Wine)
during RTL pass: final
gcc.dg/stack-check-16.c:36:1: internal compiler error: in
i386_pe_seh_unwind_emi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779
--- Comment #5 from zach-gcc at cs dot stanford.edu ---
Thanks for the quick response, I've tried it out and it looks good to me!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108657
--- Comment #14 from David Binderman ---
After five hours of reduction, cvise has:
crc32_tab[256];
unsigned crc32_context = 4294967295;
void crc32_byte(b) {
crc32_context = crc32_context >> 8 ^ crc32_tab[(crc32_context ^ b) & 255];
}
void tra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
--- Comment #9 from Segher Boessenkool ---
(In reply to Jakub Jelinek from comment #7)
> Created attachment 54460 [details]
> gcc13-pr108787.patch
That patch is preapproved, but please add a comment (before umaddditi4)
saying we do not want mad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
--- Comment #8 from Segher Boessenkool ---
(In reply to Jakub Jelinek from comment #6)
> we used to emit in GCC 12 4/4/4/5 instructions:
> mulld 9,3,4
> mulhdu 4,3,4
> addc 3,9,5
> adde 4,4,6
> and
> mulld
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
--- Comment #7 from Jakub Jelinek ---
Created attachment 54460
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54460&action=edit
gcc13-pr108787.patch
Patch that kills maddditi4 in addition to fixing umaddditi4. As mentioned
above, in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108788
--- Comment #1 from Andrew Pinski ---
I suspect this is related to the C++ paper:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1787r6.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779
--- Comment #4 from Andrew Pinski ---
(In reply to ktkachov from comment #3)
> Created attachment 54459 [details]
> Candidate patch
>
> Patch that implements -mtp= similar to clang if you have the capability to
> try it out
My only comment is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108793
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108795
Bug ID: 108795
Summary: [10/11/12/13 Regression] ICE in prep_operand, at
cp/call.cc:6325
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108794
Bug ID: 108794
Summary: ICE in determine_visibility, at cp/decl2.cc:2839
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108791
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-02-14
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108793
Bug ID: 108793
Summary: [12/13 Regression] ICE: verify_gimple failed
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108792
Bug ID: 108792
Summary: [10/11/12/13 Regression] ICE in
reset_sched_cycles_in_current_ebb, at
sel-sched.cc:7147
Product: gcc
Version: 13.0
Status: UN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97972
--- Comment #7 from G. Steinmetz ---
It gives an ICE for some target processors like -mtune=skylake,
but not for others like -mtune=sandybridge :
$ gcc-13-20230212 -c 20161124-1.c -O2 -mtune=skylake -fsanitize=undefined
-fvar-tracking-assignmen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108791
Andrew Pinski changed:
What|Removed |Added
Component|c |tree-optimization
Target Milestone|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108791
G. Steinmetz changed:
What|Removed |Added
Target||x86_64-pc-linux-gnu
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108791
Bug ID: 108791
Summary: [12/13 Regression] ICE: verify_gimple failed
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
--- Comment #6 from Jakub Jelinek ---
--- gcc/config/rs6000/rs6000.md.jj 2023-01-16 11:52:16.036734757 +0100
+++ gcc/config/rs6000/rs6000.md 2023-02-14 19:46:13.915782702 +0100
@@ -3231,20 +3231,38 @@
(plus:TI
(mult:TI (an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
Segher Boessenkool changed:
What|Removed |Added
Last reconfirmed||2023-02-14
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108790
Bug ID: 108790
Summary: bpf: gcc emits malformed ldxdw instruction at -O2
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
Jakub Jelinek changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673
--- Comment #4 from Christian Franke ---
I get similar results with x86_64-pc-cygwin-gcc (aka gcc) 11.3.0 and
x86_64-w64-mingw32-gcc 11.3.0, both from current Cygwin distro and with
x86_64-w64-mingw32-gcc (aka gcc) 12.2.0 from current MSYS2 dist
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
--- Comment #3 from Jakub Jelinek ---
--- gcc/config/rs6000/rs6000.md.jj 2023-01-16 11:52:16.036734757 +0100
+++ gcc/config/rs6000/rs6000.md 2023-02-14 18:53:25.071014954 +0100
@@ -3231,20 +3231,26 @@
(plus:TI
(mult:TI (an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108789
Andrew Pinski changed:
What|Removed |Added
Component|c |middle-end
--- Comment #1 from Andrew P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108789
Bug ID: 108789
Summary: __builtin_(add|mul)_overflow methods generate
duplicate operations if both operands are const
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108699
--- Comment #2 from Segher Boessenkool ---
Right, it needs a vpopcntb or similar first.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673
amy.mclaughlin at iar dot com changed:
What|Removed |Added
CC||amy.mclaughlin at iar dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
--- Comment #2 from Jakub Jelinek ---
In *.optimized dump it looks correct:
d_16 = h2_14(D) w* s1_15(D);
_19 = WIDEN_MULT_PLUS_EXPR ;
d0_17 = WIDEN_MULT_PLUS_EXPR ;
where WIDEN_MULT_EXPR has 2 64-bit unsigned operands and 128-bit result, a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
--- Comment #1 from Jakub Jelinek ---
Correction, -fPIC isn't important. Even more reduced testcase:
__attribute__((noipa)) unsigned __int128
foo (unsigned long long h0, unsigned long long h1, unsigned long long h2,
unsigned long long r0, unsig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108788
Bug ID: 108788
Summary: Lookup of injected class name should be type-dependent
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |13.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108787
Bug ID: 108787
Summary: [13 Regression] libsodium miscompilation on power9
starting with r13-2107
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: norm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108761
--- Comment #7 from Paul Robinson
---
Okay. I'm persuaded this is not a great idea, and I'll solve the customer's
problem another way.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108657
--- Comment #13 from David Binderman ---
I tried adding flag 1 to the run of the two binaries. Here is
the bash history:
1003 gcc bug880.c
1004 ./a.out > /tmp/0
1005 ~/gcc/results/bin/gcc -w -O3 -ftrivial-auto-var-init=zero bug880.c -o
b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108679
--- Comment #4 from Martin Jambor ---
I have proposed the fix on the mailing list:
https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611978.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108786
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-02-14
Assignee|unassign
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108786
Bug ID: 108786
Summary: bitmap_first_set_bit misses a bitmap_clear_first_bit
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532
--- Comment #10 from Marek Polacek ---
Sorry. A patch is on review.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532
ecurtin at redhat dot com changed:
What|Removed |Added
CC||ecurtin at redhat dot com
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108779
--- Comment #3 from ktkachov at gcc dot gnu.org ---
Created attachment 54459
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54459&action=edit
Candidate patch
Patch that implements -mtp= similar to clang if you have the capability to try
it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71954
Jonathan Wakely changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108772
--- Comment #5 from Richard Biener ---
Btw, the limbo DIE is created via
#0 new_die (tag_value=DW_TAG_variable, parent_die=,
t=)
at /home/rguenther/src/trunk/gcc/dwarf2out.cc:5882
#1 0x00e006ad in gen_variable_die (
decl=
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108699
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2023-02-14
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108782
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108772
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108782
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:994224236e0231807681b62e880d3c2772c69521
commit r13-5983-g994224236e0231807681b62e880d3c2772c69521
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108729
--- Comment #3 from Kewen Lin ---
PR108731 has another test case gcc.target/powerpc/bfp/vec-test-data-class-9.c
which needs to be updated too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108729
--- Comment #2 from Kewen Lin ---
*** Bug 108731 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108731
Kewen Lin changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108731
Kewen Lin changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108729
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2023-02-14
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108777
--- Comment #8 from Marco Elver ---
Thanks for the quick turnaround!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108777
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
1 - 100 of 115 matches
Mail list logo
