https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82251
--- Comment #2 from GCC Commits ---
The trunk branch has been updated by Thomas Schwinge :
https://gcc.gnu.org/g:fa90febea9801d4255bf6a1e9f0fd998629c3c7c
commit r15-4348-gfa90febea9801d4255bf6a1e9f0fd998629c3c7c
Author: Thomas Schwinge
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116749
Sam James changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment #7 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117138
--- Comment #3 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:28982c271cbbed3580e4c7c784892694c3b6b2de
commit r15-4351-g28982c271cbbed3580e4c7c784892694c3b6b2de
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117147
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117149
Bug ID: 117149
Summary: GCC's optimizer intermittently generates erroneous
thread-local storage code, causing segmentation fault
Product: gcc
Version: 14.2.1
Status: UNC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116749
Sam James changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117147
--- Comment #5 from Andrew Pinski ---
Reducing it right now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117148
--- Comment #4 from LIU Hao ---
>From the code we can see that the call is unconditional; it must happen, so is
not 'unlikely'. On the other hand, `atomic_cmpxchg_iptr` is more complex but
surprisingly it is able to be inlined.
And yes, changin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117149
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82250
--- Comment #7 from GCC Commits ---
The trunk branch has been updated by Thomas Schwinge :
https://gcc.gnu.org/g:fa90febea9801d4255bf6a1e9f0fd998629c3c7c
commit r15-4348-gfa90febea9801d4255bf6a1e9f0fd998629c3c7c
Author: Thomas Schwinge
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116907
--- Comment #33 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:7d15248d41dc45a4ba2d38ff532b672a5c0651d0
commit r15-4355-g7d15248d41dc45a4ba2d38ff532b672a5c0651d0
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116907
Richard Biener changed:
What|Removed |Added
Known to fail|15.0|
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117054
--- Comment #3 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:bb2bfdb2048aed18ef7dc01b51816a800e83ce54
commit r15-4365-gbb2bfdb2048aed18ef7dc01b51816a800e83ce54
Author: Patrick Palka
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116710
--- Comment #1 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:8161c4adea7f1842f9d28633d82e912ebb7a4cf9
commit r15-4366-g8161c4adea7f1842f9d28633d82e912ebb7a4cf9
Author: Patrick Palka
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116710
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116891
--- Comment #12 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:4366f0c7e296ea0d7279343c9b0a1d597588a1da
commit r15-4367-g4366f0c7e296ea0d7279343c9b0a1d597588a1da
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80637
--- Comment #7 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:b110e092d260906432931796c1d96cba305c60e4
commit r15-4368-gb110e092d260906432931796c1d96cba305c60e4
Author: Patrick Palka
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
--- Comment #4 from mauro russo ---
ok, thank you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-10-15
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117116
--- Comment #16 from Uroš Bizjak ---
Fixed on mainline, will be backported to other release branches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68350
Jonathan Wakely changed:
What|Removed |Added
Keywords||patch
--- Comment #17 from Jonathan Wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115444
--- Comment #11 from Jonathan Wakely ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665537.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #67 from Julian Waters ---
Command line used in compiling the reproducer: xgcc -O2 -S -std=c11 -pedantic
-Wpedantic tls.c
The thing that has me puzzled is that the main differences between both patches
are in the load of the primary
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
--- Comment #1 from Jonathan Wakely ---
The blog post is wrong, GCC is behaving as intended.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #5 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #4)
> (and Richard Smith aid so in
*said so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117116
--- Comment #15 from GCC Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:80d7032067a3a5b76aecd657d9b35b0a8f5a941d
commit r15-4359-g80d7032067a3a5b76aecd657d9b35b0a8f5a941d
Author: Uros Bizjak
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111425
Frank Scheiner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117158
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
Target Mi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #3 from Carlos Galvez ---
Please note that this ticket is about protected *destructor*. For protected
*constructor*, clang has same behavior as GCC.
CWG 2244 does not appear to consider this case?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117154
--- Comment #4 from Jonathan Wakely ---
Why should access to a protected destructor be different to access to a
protected constructor? It's obviously related (and Richard Smith aid so in the
llvm issue too).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117157
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109642
Andrew Pinski changed:
What|Removed |Added
CC||dimitry@unified-streaming.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116627
Frank Scheiner changed:
What|Removed |Added
CC||frank.scheiner at web dot de
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111645
--- Comment #7 from Carl Love ---
Patch committed that add the signed __int128 and unsigned __int128 argument
types for the
overloaded built-ins vec_sld, vec_sldb, vec_sldw, vec_sll, vec_slo, vec_srdb,
vec_srl,
vec_sr0 built-ins was committed:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117166
--- Comment #1 from Sam James ---
It's very sensitive even if e.g. copying all the headers locally. Rather than
faff more, I'll try reduce it by hand first.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108250
Sam James changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117165
Bug ID: 117165
Summary: ICE: in extract_insn, at recog.c:2311 unrecognizable
insn: UNSPECV_FNSTSW with -mgeneral-regs-only and
__builtin_ia32_fnstsw()
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117166
Bug ID: 117166
Summary: [15 regression] ICE when building lxml-5.3.0 with LTO
(linemap_line_start, at libcpp/line-map.cc:949)
Product: gcc
Version: 15.0
Status: UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113952
Sam James changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from Sam James ---
Pa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117128
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116510
--- Comment #13 from rguenther at suse dot de ---
On Tue, 15 Oct 2024, ak at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116510
>
> --- Comment #12 from ak at gcc dot gnu.org ---
> Like this? It fixes the test case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117159
--- Comment #2 from Hongtao Liu ---
typedef __attribute__((__vector_size__ (4))) unsigned char W;
typedef __attribute__((__vector_size__ (64))) int V;
typedef __attribute__((__vector_size__ (64))) long long Vq;
W w;
V v;
Vq vq;
static inline W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117160
Bug ID: 117160
Summary: [15 regression] GCC trunk generates larger code than
GCC 14 at -Os/-Oz (progressed in 14)
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117161
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
Andrew Pinski changed:
What|Removed |Added
CC||Robert.Hardwick at arm dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
Sam James changed:
What|Removed |Added
Target Milestone|--- |15.0
--- Comment #69 from Sam James ---
Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117164
Bug ID: 117164
Summary: ICE building gcc.dg/nested-func-12.c with -std=gnu23
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #3 from Paul Caprioli ---
Note that this is not for me; it's for everybody else.
The idea is for this to be the standard macro for specifying the IEEE rounding
to nearest attribute `roundTiesToEven`.
My contacts at Intel tell me the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117162
Joseph S. Myers changed:
What|Removed |Added
Last reconfirmed||2024-10-16
Status|UNCONFI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #4 from Andrew Pinski ---
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/657957.html
Adding a new macro for GCC 15 won't fix many many older compilers out there. So
most code will still use the old name for many many years to c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
--- Comment #5 from Andrew Pinski ---
Also bugzilla is not to track already submitted patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117156
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117150
Eric Gallager changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115365
--- Comment #9 from GCC Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:a8b4ea1bcc10b5253992f4b932aec6862aef32fa
commit r15-4371-ga8b4ea1bcc10b5253992f4b932aec6862aef32fa
Author: liuhongt
Date: Tue Oct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117159
Hongtao Liu changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |liuhongt at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116994
Davide Italiano changed:
What|Removed |Added
CC||lingling.kong7 at gmail dot com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #401 from Oleg Endo ---
It seems there is a silent wrong-code bug somewhere when building some
Dreamcast projects with LRA and LTO enabled. It results in wrong graphics
being output. So far could not isolate the wrong-code though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117163
Bug ID: 117163
Summary: Missing macro to round to nearest floating-point value
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117162
Bug ID: 117162
Summary: Universal character names designating members of the
basic character set or control characters should be
allowed in string literals or character constants
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
--- Comment #67 from GCC Commits ---
The master branch has been updated by Qing Zhao :
https://gcc.gnu.org/g:e7380688fa5917011c3fb85b5e06fb00f776a95d
commit r15-4370-ge7380688fa5917011c3fb85b5e06fb00f776a95d
Author: Qing Zhao
Date: Tue Oct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117161
--- Comment #1 from Robert Hardwick ---
Created attachment 59354
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59354&action=edit
Preprocessed source stored into /tmp/ccEF5DEn.out file, please attach this to
your bugreport.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117161
Bug ID: 117161
Summary: internal compiler error: in
vect_get_vector_types_for_stmt, at
tree-vect-stmts.c:12252 on gcc 10.2 for aarch64+sve
Product: gcc
Version:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116016
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117123
Davide Italiano changed:
What|Removed |Added
CC||pheeck at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117008
--- Comment #13 from Matt Bentley ---
Bool C-arrays also display the same problem, but only if a warm-up loop is
present before the main loop (to 'warm up' the cache). I discovered this by
accident the other day. char arrays and int arrays did n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117008
--- Comment #14 from Matt Bentley ---
Created attachment 59355
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59355&action=edit
.ii file for vector code causing same issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117008
--- Comment #15 from Matt Bentley ---
Created attachment 59356
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59356&action=edit
.ii file for bool[array] causing same issue
101 - 172 of 172 matches
Mail list logo