https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112431
--- Comment #15 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:7e854b58084c131fceca9e8fa9dcc7469972e69d
commit r14-6400-g7e854b58084c131fceca9e8fa9dcc7469972e69d
Author: Juzhe-Zhong
Date: Sat Dec 9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110606
--- Comment #10 from Jeevitha ---
The following instructions [in basic block 4] were removed in sched2 DCE, which
makes r3 unused [populated in call_insn 26], but they were not deleted in this
pass itself:
(insn 28 26 29 4 (set (reg:DI 9 9 [132
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101852
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-12-11
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112951
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
--- Comment #11 from Steve Kargl ---
On Sun, Dec 10, 2023 at 09:45:33PM +, anlauf at gcc dot gnu.org wrote:
>
> here's a minor update that fully removes the "Extended math intrinsics" node.
> Otherwise your patch would not compile here.
On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112951
Bug ID: 112951
Summary: [14 Regression] cond_copysign, cond_len_copysign optab
not documented
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: document
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101852
--- Comment #5 from Andrew Pinski ---
A new one for GCC 14 even:
cond_copysign
cond_len_copysign
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112950
Bug ID: 112950
Summary: gcc.target/aarch64/sve/acle/general/dupq_5.c fails on
aarch64_be-linux-gnu
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: tes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104234
--- Comment #2 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:ab3daffcbf35566d468c3028e48068a481048baf
commit r14-6394-gab3daffcbf35566d468c3028e48068a481048baf
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100470
--- Comment #7 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:4719b6f5ae4d758f193a17bbd5fb6cbacd702a23
commit r14-6395-g4719b6f5ae4d758f193a17bbd5fb6cbacd702a23
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96090
--- Comment #3 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:4719b6f5ae4d758f193a17bbd5fb6cbacd702a23
commit r14-6395-g4719b6f5ae4d758f193a17bbd5fb6cbacd702a23
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53025
--- Comment #9 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:4719b6f5ae4d758f193a17bbd5fb6cbacd702a23
commit r14-6395-g4719b6f5ae4d758f193a17bbd5fb6cbacd702a23
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112580
--- Comment #2 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:ab3daffcbf35566d468c3028e48068a481048baf
commit r14-6394-gab3daffcbf35566d468c3028e48068a481048baf
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112929
--- Comment #12 from Li Pan ---
(In reply to Patrick O'Neill from comment #0)
> Testcase:
> int printf(char *, ...);
> int a, b, l, i, p, q, t, n, o;
> int *volatile c;
> static int j;
> static struct pack_1_struct d;
> long e;
> char m = 5;
> s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112904
Hongtao Liu changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112904
--- Comment #3 from GCC Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:2c2df123de432356d28ee7e8a9627dc9e80a399d
commit r14-6393-g2c2df123de432356d28ee7e8a9627dc9e80a399d
Author: liuhongt
Date: Fri Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947
--- Comment #4 from resence at parsoma dot net ---
Or rather,
static int *nimErrorFlag(void) {
/* With this, no always-false warning */
/* printf("BAR1: %p\n", (void*)&nimInErrorMode__system_u4299); */
if (((&nimInErrorMode__system_u4299)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947
--- Comment #3 from resence at parsoma dot net ---
It's not only the null pointer check per se though?
Re-add a stdio.h import for convenience, and it still vacillates whether or not
that address is NULL or not:
BAR2: 0x7f25d843173c
BAR3: 0x7f2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112707
HaoChen Gui changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112707
--- Comment #16 from GCC Commits ---
The master branch has been updated by HaoChen Gui :
https://gcc.gnu.org/g:ae226cb1ee17d61c416c9d4d8c5a142788b8afff
commit r14-6392-gae226cb1ee17d61c416c9d4d8c5a142788b8afff
Author: Haochen Gui
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112707
--- Comment #15 from GCC Commits ---
The master branch has been updated by HaoChen Gui :
https://gcc.gnu.org/g:46e342b985e6b4058db73875103cced2666e84e2
commit r14-6391-g46e342b985e6b4058db73875103cced2666e84e2
Author: Haochen Gui
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95656
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95656
--- Comment #4 from Andrew Pinski ---
* See also PR79265 and PR98109
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95656
Andrew Pinski changed:
What|Removed |Added
CC||resence at parsoma dot net
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947
--- Comment #1 from Andrew Pinski ---
This is by design.
-fsanitize=undefined turns off -fdelete-null-pointer-checks .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
--- Comment #7 from Andrew Pinski ---
Specifically https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32455#c4 .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
--- Comment #13 from Zeb Figura ---
(In reply to Sam James from comment #11)
> (In reply to Jens-Hanno Schwalm from comment #10)
> > Hi, i think we found a very-similar issue in darktable code, you might look
> > at
> >
> > https://github.com/d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
--- Comment #5 from Andrew Pinski ---
Oh the definition of __builtin_clz does not have return value so the value is
undefined to begin with.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
--- Comment #3 from Krister Walfridsson ---
The C program is obviously UB. But the optimization is done on GIMPLE, and it
is not obvious to me that the GIMPLE code is UB -- we have a function called
__builtin_clz that calls an internal function,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
--- Comment #2 from Andrew Pinski ---
defining __builtin_clz makes this code undefined. Especially when it comes to
calling itself.
That is the ranges here are ok and correct but rather the usage is undefined.
gcc.dg/pr100521.c is just testing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
--- Comment #1 from Andrew Pinski ---
I think the testcase is broken rather than anything else.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112949
Bug ID: 112949
Summary: evrp produces incorrect range for __builtin_clz
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112948
Bug ID: 112948
Summary: gcc/config/aarch64/aarch64-early-ra.cc:1953: possible
cut'n'paste error ?
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: norm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112947
Bug ID: 112947
Summary: Contradictory indications of extern __thread address
NULL or not with UBSAN
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
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=105543
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|ASSI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111503
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
--- Comment #6 from Jonathan Wakely ---
If you can reply on gcc-patches (CCing the libstdc++ list) that would be great,
thanks for looking at it!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
--- Comment #5 from Nate Eldredge ---
Oh wait, disregard that last, I realized that I only applied one of the two
patches. Let me try again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
--- Comment #4 from Nate Eldredge ---
@Jonathan: I think that patch set is on the right track, but it has some other
serious bugs. For one, __atomic_wait_address calls __detail::__wait_impl with
__args._M_old uninitialized (g++ -O3 -Wall catche
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112880
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112881
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|11.5|13.3
Status|ASSI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105220
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
Sum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93762
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
--- Comment #17 from GCC Commits ---
The releases/gcc-13 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff
commit r13-8142-g7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93762
--- Comment #6 from GCC Commits ---
The releases/gcc-13 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff
commit r13-8142-g7a2f4af9b1b12d8b1f1b4cf4ddb812f2a48ce9ff
Author: Harald Anlauf
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112946
Bug ID: 112946
Summary: Assignment of string to enumeration or set crashes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111972
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
--- Comment #12 from Andrew Pinski ---
(In reply to Sam James from comment #11)
> (In reply to Jens-Hanno Schwalm from comment #10)
> > Hi, i think we found a very-similar issue in darktable code, you might look
> > at
> >
> > https://github.co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
--- Comment #11 from Sam James ---
(In reply to Jens-Hanno Schwalm from comment #10)
> Hi, i think we found a very-similar issue in darktable code, you might look
> at
>
> https://github.com/darktable-org/darktable/pull/15742
>
If you're hitt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112933
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112931
Richard Sandiford changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112930
Richard Sandiford changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112931
--- Comment #3 from GCC Commits ---
The trunk branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:b3aed459634654d295a1d00e6c149565ced7a9a2
commit r14-6387-gb3aed459634654d295a1d00e6c149565ced7a9a2
Author: Richard Sandiford
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112933
--- Comment #2 from GCC Commits ---
The trunk branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:b3aed459634654d295a1d00e6c149565ced7a9a2
commit r14-6387-gb3aed459634654d295a1d00e6c149565ced7a9a2
Author: Richard Sandiford
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112930
--- Comment #3 from GCC Commits ---
The trunk branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:f5c8d6bc050a8a6120aff2be25b6892d91baac99
commit r14-6386-gf5c8d6bc050a8a6120aff2be25b6892d91baac99
Author: Richard Sandiford
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111503
--- Comment #3 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:99c5fa3ba6b5f54a7d632bd9da0e07dd85a4b669
commit r14-6382-g99c5fa3ba6b5f54a7d632bd9da0e07dd85a4b669
Author: Harald Anlauf
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112945
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105543
--- Comment #4 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:1e462fb480d38de5f9a4578bbe5c5bc66a01a9ed
commit r14-6381-g1e462fb480d38de5f9a4578bbe5c5bc66a01a9ed
Author: Harald Anlauf
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112468
--- Comment #8 from Andrew Pinski ---
*** Bug 112945 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
--- Comment #4 from Xi Ruoyao ---
On LA664:
19970.709626 -falign-labels=4 -falign-functions=16 -falign-loops=64
-falign-jumps=16
19970.709626 -falign-labels=4 -falign-functions=32 -falign-loops=32
-falign-jumps=16
19976.028765 -fali
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
Jens-Hanno Schwalm changed:
What|Removed |Added
CC||ha...@schwalm-bremen.de
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112945
Bug ID: 112945
Summary: FAIL: gcc.dg/tree-ssa/phi-opt-24.c scan-tree-dump-not
phiopt2 "if"
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
--- Comment #3 from Xi Ruoyao ---
Top 10 configurations on LA464 for Coremark:
12757.542897 -falign-labels=4 -falign-functions=8 -falign-loops=32
-falign-jumps=32
12763.241863 -falign-labels=4 -falign-functions=64 -falign-loops=32
-fali
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92606
--- Comment #24 from Georg-Johann Lay ---
(In reply to Richard Biener from comment #22)
> Should be fixed on trunk. Confirmation would be nice (checked x86 only).
Tested with: gcc version 14.0.0 20231210 (experimental) (GCC)
Still fails
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104928
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2023-12-10
CC|
Li Pan ---
(In reply to JuzheZhong from comment #8)
> Li Pan will investigate it. He will note me if there is a bug in vsetvl pass.
The interesting thing is that I cannot fully reproduce this with build
20231210.
PASS >> ../build-qemu/qemu-riscv64 -cpu rv64,vlen=128,v=true,vext_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112942
--- Comment #6 from Jonathan Wakely ---
(In reply to Andrew Pinski from comment #4)
> Just giving background information of the wording changes to C++17 on
> std::variant and std::swap here and about the testcase you pointed to and
> about when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112942
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Summary|swap(variant&, v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112758
--- Comment #12 from Segher Boessenkool ---
(In reply to Eric Botcazou from comment #11)
> > It says those upper bits are well-defined, i.e. whatever MD pattern is used
> > for it eventually will emit machine code that has the exact same result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112944
Georg-Johann Lay changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |gjl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112944
Bug ID: 112944
Summary: AVR: Support .rodata in Flash for Devices with FLMAP
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92606
--- Comment #23 from Georg-Johann Lay ---
(In reply to Richard Biener from comment #22)
> Should be fixed on trunk. Confirmation would be nice (checked x86 only).
For AVR, this does not fix the attribute progmem case (for which it was
originall
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80878
--- Comment #43 from admin_public at liblfds dot org ---
> I tested CMPXCHG16B with inline assembly on an i7-1165G7 (Dell XPS 13 9305)
> and it turned out to be much slower than CMPXCHG, even slower than a pair of
> calls to `pthread_mutex_lock(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80878
--- Comment #42 from LIU Hao ---
(In reply to Yongwei Wu from comment #27)
> Anyone can show a valid use case for a non-lock-free version of 128-bit
> atomic_compare_exchange?
>
> I am trying to use it in a data structure intended to be lock-fre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112943
Bug ID: 112943
Summary: ICE: in gen_reg_rtx, at emit-rtl.cc:1176 with -O2
-march=westmere -mapxf
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: ice-o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112935
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106260
--- Comment #5 from Zdenek Sojka ---
Created attachment 56843
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56843&action=edit
slightly reduced testcase
$ x86_64-pc-linux-gnu-gcc -O2 -fno-unit-at-a-time -fwhole-program testcase.C
during I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111867
--- Comment #9 from Andrew Pinski ---
Patch submitted:
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640028.html
83 matches
Mail list logo