https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677
--- Comment #18 from Gianfranco ---
Created attachment 57159
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57159=edit
unreduced testcase
// works: /usr/lib/gcc-snapshot/bin/gcc -O3 -fstack-protector-strong -fopenmp
-ffast-math
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #7 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #6)
> (In reply to Hirthammer from comment #5)
> > This whole thing with std::format and std::chrono::time_point is currently a
> > total minefield.
>
> That
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113312
--- Comment #26 from H.J. Lu ---
(In reply to Xin Li from comment #25)
> (In reply to Xin Li from comment #22)
> > Per Peter's suggestion, I added __attribute__((no_callee_saved_registers))
> > to a linux source tree containing FRED patches:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #6 from Jonathan Wakely ---
(In reply to Hirthammer from comment #5)
> This whole thing with std::format and std::chrono::time_point is currently a
> total minefield.
That seems like an exaggeration.
> In MSVC it is even more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113467
--- Comment #16 from Richard Biener ---
Also eventually see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113364#c9 - a
pending fix for a wrong-code issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113490
--- Comment #4 from Richard Biener ---
(In reply to Jakub Jelinek from comment #2)
> Started with r14-285-g7bcdcf86e8272eeb524cc1dcb0ada8c8cfe6f27e
Should have only exposed this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #5 from hirtham...@allterra-dno.de ---
(In reply to Jonathan Wakely from comment #4)
> MSVC rejects this the same way, although libc++ from LLVM 17 compiles it.
>
> AFAICT std::format("{}", tp) would be invalid because that formats
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113503
Jakub Jelinek changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113503
Bug ID: 113503
Summary: [14 Regression] xtb test miscompilation starting with
r14-870
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113490
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113352
Eric Botcazou changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #4 from Jonathan Wakely ---
MSVC rejects this the same way, although libc++ from LLVM 17 compiles it.
AFAICT std::format("{}", tp) would be invalid because that formats tp by
writing to a stream, and there is no operator<< for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102051
Vaci changed:
What|Removed |Added
CC||vaci at vaci dot org
--- Comment #5 from Vaci
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113467
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113490
Jakub Jelinek changed:
What|Removed |Added
Summary|[14 Regression] ICE: in |[14 Regression] ICE: in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113351
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113350
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113502
Andrew Pinski changed:
What|Removed |Added
Summary|gcc.target/aarch64/vect-ear |gcc.target/aarch64/vect-ear
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113478
--- Comment #3 from Richard Biener ---
(In reply to Jan Hubicka from comment #2)
> Probably is_inexpensive_bulitin_p should return true here?
Possibly, at least when we know it doesn't expand to a libatomic call? OTOH
even then a function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113502
Bug ID: 113502
Summary: gcc.target/aarch64/vect-early-break-cbranch.c testcase
is too sensitive
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113478
--- Comment #2 from Jan Hubicka ---
Probably is_inexpensive_bulitin_p should return true here?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #26 from rguenther at suse dot de ---
On Fri, 19 Jan 2024, juzhe.zhong at rivai dot ai wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
>
> --- Comment #22 from JuzheZhong ---
> (In reply to Richard Biener from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113114
--- Comment #7 from Alex Coplan ---
Testing a fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111475
--- Comment #5 from Rainer Orth ---
Created attachment 57157
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57157=edit
Linux testcase: as1-lx.ii
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111475
--- Comment #4 from Rainer Orth ---
Created attachment 57156
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57156=edit
Solaris testcase: as1-sol2.ii
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111475
--- Comment #3 from Rainer Orth ---
I've now reduced c-c++-common/analyzer/allocation-size-1.c:test_2 to minimal
preprocessed the inputs, still showing the difference:
$ cc1plus -fpreprocessed as1-sol2.ii -quiet -std=c++98
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #25 from JuzheZhong ---
RISC-V backend memory-hog issue is fixed.
But compile time hog in LICM still there, so keep this PR open.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #24 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:01260a823073675e13dd1fc85cf2657a5396adf2
commit r14-8282-g01260a823073675e13dd1fc85cf2657a5396adf2
Author: Juzhe-Zhong
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113442
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113488
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113494
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113488
--- Comment #9 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:62b59bc4f70d02a485c527aa3277f4b4010edb6b
commit r14-8281-g62b59bc4f70d02a485c527aa3277f4b4010edb6b
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113494
--- Comment #3 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:6ce7008cfa1a240895ecca0898e7dbaecd975567
commit r14-8280-g6ce7008cfa1a240895ecca0898e7dbaecd975567
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110422
--- Comment #5 from Martin Jambor ---
Fixed on trunk, I plan to backport to open release branches in the upcoming
weeks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #23 from Kito Cheng ---
> I am considering whether we should disable LICM for RISC-V by default if
> vector is enabled ?
That's will cause regression for other program, also may hurt those program not
vectorized but benefited from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #22 from JuzheZhong ---
(In reply to Richard Biener from comment #21)
> I once tried to avoid df_reorganize_refs and/or optimize this with the
> blocks involved but failed.
I am considering whether we should disable LICM for RISC-V
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #21 from Richard Biener ---
I once tried to avoid df_reorganize_refs and/or optimize this with the blocks
involved but failed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
Richard Biener changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113498
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113089
Alex Coplan changed:
What|Removed |Added
URL||https://patchwork.sourcewar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113494
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113492
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337
--- Comment #14 from Saurabh Jha ---
I will look into this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113501
--- Comment #1 from cqwrteur ---
https://github.com/gcc-mirror/gcc/blob/56778b69ce558bb7e3ab7c561ee4ee48ac20263b/gcc/config/i386/mingw32.h#L192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113501
Bug ID: 113501
Summary: i think -lntdll should by default by included in
windows targets
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113464
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113463
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113459
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113464
--- Comment #3 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:ee2aa93e9cd0d62f840cb6614c3cd12c15301a72
commit r14-8278-gee2aa93e9cd0d62f840cb6614c3cd12c15301a72
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113463
--- Comment #2 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:df1cd90e32bb17d34f5fdce99bd0377fe1b8e5c6
commit r14-8277-gdf1cd90e32bb17d34f5fdce99bd0377fe1b8e5c6
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113459
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:dcd5601c2b7298155c9a8e1bfb93ee8e952eca0b
commit r14-8276-gdcd5601c2b7298155c9a8e1bfb93ee8e952eca0b
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113490
Richard Biener changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #18 from Rainer Orth ---
Created attachment 57155
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57155=edit
32-bit sparc-sun-solaris2.11 pr113431.c.185t.slp1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
Rainer Orth changed:
What|Removed |Added
CC||ro at gcc dot gnu.org
--- Comment #17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113488
--- Comment #8 from Jakub Jelinek ---
(In reply to Richard Biener from comment #7)
> interesting enough we didn't generate a DIE for the LABEL_DECL for the
> abstract instance DIE. Instead we just have
Maybe because of -g1?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113488
--- Comment #7 from Richard Biener ---
OK, so it's of course set_decl_origin_self () invoked via
#0 set_decl_origin_self (decl=)
at /home/rguenther/src/trunk/gcc/dwarf2out.cc:23321
#1 0x014ddc14 in set_block_origin_self (stmt=)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113450
--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #4 from Jonathan Wakely ---
> I pushed a slightly different change, but it should be equivalent. Please
> reopen if I messed it up :-)
The variant worked just fine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #19 from JuzheZhong ---
(In reply to JuzheZhong from comment #18)
> Hi, Robin.
>
> I have fixed patch for memory-hog:
> https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643418.html
>
> I will commit it after the testing.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
--- Comment #7 from Jakub Jelinek ---
r14-263-gd53b3d94aaf211ffb2159614f5aaaf03ceb861cc in particular
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495
--- Comment #18 from JuzheZhong ---
Hi, Robin.
I have fixed patch for memory-hog:
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643418.html
I will commit it after the testing.
But compile-time hog still exists which is loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
Sam James changed:
What|Removed |Added
See Also||https://reviews.llvm.org/D1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64064
--- Comment #2 from LIU Hao ---
It looks that MS STL calls `_fseeki64(fp, ...)` [1], while libstdc++ calls
`lseek(_fileno(fp), ...)` [2].
The seek operation shall take the buffering of `FILE` struct into account,
hence I think the libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #3 from hirtham...@allterra-dno.de ---
Sorry, for the missing includes.
> Since this is a bug in libstdc++ headers it's not at all surprising that you
> get
> the same error with any compiler using those headers. This should not
101 - 163 of 163 matches
Mail list logo