https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110965
--- Comment #2 from Andrew Pinski ---
Blah, here is a testcase which shows this is causing a regression in GCC 14
(after r14-1597-g64d90d06d2db43):
```
bool f(long long l){
int t = (int)l;
if (t == 1)
return true;
if (t == 2)
return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #92 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:b129d6b5f5f13995d57d677afcb3e94d0d9c327f
commit r14-3119-gb129d6b5f5f13995d57d677afcb3e94d0d9c327f
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #93 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:d5ad55a83d504df582d1e6f1c168454a028c0437
commit r14-3120-gd5ad55a83d504df582d1e6f1c168454a028c0437
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110967
Bug ID: 110967
Summary: c++20 coroutine does not support SIMD avx2 and avx512
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110967
--- Comment #1 from Zhuhe Fang ---
also discussed on
https://stackoverflow.com/questions/76727854/c-coroutine-runs-avx-simd-code-but-causes-sigsegv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104177
Andrew Pinski changed:
What|Removed |Added
CC||fangzhuhe at 126 dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110967
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110419
Mikael Morin changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110966
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
--- Comment #1 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110968
Bug ID: 110968
Summary: format out of bounds read on format("{:05L}",-1.f)
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110966
--- Comment #2 from Hongtao.liu ---
(In reply to Richard Biener from comment #1)
> I think matmul is fine with avx512f or avx, so requiring/using only the base
> ISA level sounds fine to me.
Could be potential miss-optimization.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110867
--- Comment #8 from Stefan Schulze Frielinghaus
---
Created attachment 55716
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55716&action=edit
Really fix narrow comparison
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110867
--- Comment #9 from Stefan Schulze Frielinghaus
---
It looks like as if the first fix didn't entirely solve the problem. It turns
out that the normal form of const_int is not always met. Before releasing a
new patch, could you test it first i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110956
--- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #8 from Thomas Neumann ---
> Created attachment 55715
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55715&action=edit
> patch to use the correct base pointer
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110969
Bug ID: 110969
Summary: ICE in to_constant, at poly-int.h:504 on aarch64
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955
--- Comment #7 from Rainer Orth ---
(In reply to Petr Sumbera from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > Are you sure this is NOT a LLVM JIT issue?
> > There was a similar issue on aarch64 too; PR 108994 which was fixed i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102587
Andrew Pinski changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110969
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110968
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
Martin Uecker changed:
What|Removed |Added
CC||muecker at gwdg dot de
--- Comment #56 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110970
Bug ID: 110970
Summary: clang / c++23 missing 'typename' prior to dependent
type name 'iterator_traits<_It>::iterator_category'
Product: gcc
Version: 13.2.1
Status: UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110876
--- Comment #4 from Dvir Yitzchaki ---
Thanks @Andrew.
Is it undefined behavior to recover from SIGABRT? I didn't find a source for
that.
The fact is that the memory ASAN is complaining about was allocated.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955
--- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #7 from Rainer Orth ---
> (In reply to Petr Sumbera from comment #3)
>> (In reply to Andrew Pinski from comment #1)
>> > Are you sure this is NOT a LLVM JIT issue?
>> > Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110956
--- Comment #10 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE Uni-Bielefeld.DE> ---
[...]
> I'm currently running a full i386-pc-solaris2.11 bootstrap.
... which just completed without reg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110963
--- Comment #3 from Richard Biener ---
So we're now doing an additional sinking:
Sinking # VUSE <.MEM_2(D)>
pretmp_12 = h;
from bb 2 to bb 4
Removing basic block 9
that's the only IL difference on GIMPLE, without this we optimize away foo
dur
/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230810 (experimental) (GCC)
[533] %
[533] % gcctk -O3 small.c
during GIMPLE pass: lsplit
small.c: In
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955
--- Comment #9 from Petr Sumbera ---
(In reply to r...@cebitec.uni-bielefeld.de from comment #8)
> > I'm not sure if we taked about this before: have you tried building SPARC
> > LLVM
> > without the JIT patch (033-solaris-LLVM-JIT.patch)? It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955
--- Comment #10 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #9 from Petr Sumbera ---
> (In reply to r...@cebitec.uni-bielefeld.de from comment #8)
>> > I'm not sure if we taked about this before: have you tried building
>> > SPARC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84510
Martin Uecker changed:
What|Removed |Added
CC||muecker at gwdg dot de
--- Comment #2 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110963
--- Comment #4 from Richard Biener ---
(In reply to Andrew Pinski from comment #1)
> Confirmed.
> PRE seems to have missed an obvious redundant load here though:
Skipping partial redundancy for expression {mem_ref<0B>,addr_expr<&h>}@.MEM_21
(00
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110963
--- Comment #5 from Theodoros Theodoridis ---
(In reply to Richard Biener from comment #4)
> Alternatively you can put __attribute__((hot)) on 'main' which we otherwise
> consider cold. Maybe that's a good idea for future DCE regression searche
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110963
--- Comment #6 from rguenther at suse dot de ---
On Thu, 10 Aug 2023, theodort at inf dot ethz.ch wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110963
>
> --- Comment #5 from Theodoros Theodoridis ---
> (In reply to Richard Biener fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108404
--- Comment #8 from Iain Sandoe ---
(In reply to Gaius Mulley from comment #7)
> I wonder if this bug has now been fixed via the other PR fixes.
> Specifically the rewrite of RTco.cc, the defensive use of select, bugfixes
> to HIGH and FIO.mod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110963
--- Comment #7 from Jan Hubicka ---
We don't consider main cold, but executed once: code out of loops is optimized
for size, but anything in loops is optimized according to -O setting. I did
not really think of users overwriting it by hot attri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102968
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #57 from Roman Krotov ---
(In reply to Ed Catmur from comment #55)
> So this problem will resolve itself, over time.
But I don't see any reasons not to implement the switch right now...
Late is better than never.
> we can expect tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110970
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110964
--- Comment #1 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:887f13916b18f46b563d527ad5001c6384e44a60
commit r14-3123-g887f13916b18f46b563d527ad5001c6384e44a60
Author: Juzhe-Zhong
Date: Thu Aug 10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65762
--- Comment #1 from Iain Sandoe ---
so, FAOD, that means that
versioned namespace => disables dual ABI
=> forces the old string impl?
What's the blocker to making it work?
(just time - or ABI issues?)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110970
--- Comment #2 from gcc-bugzilla at zulan dot net ---
Yes, apologies for the missing information
clang version 15.0.7
g++ (GCC) 13.2.1 20230801
(Arch)
According to https://clang.llvm.org/cxx_status.html
P0634R3 / "Down with typename!" is implem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108404
Gaius Mulley changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108835
--- Comment #10 from Iain Sandoe ---
(In reply to Gaius Mulley from comment #9)
> This looks fixed from the commit trail - can this PR be closed now?
It's "fixed" - in that the more defensive coding around the select calls no
longer triggers th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110970
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65762
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed|2015-04-14 00:00:00 |2023-8-10
Depends on|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83077
Jonathan Wakely changed:
What|Removed |Added
Keywords||patch
Last reconfirmed|2017-11-20 00
สวัสดีครับ บริษัท เอกทรัพย์เจริญ เครดิต
*บริการเงินทุนฉุกเฉินระยะสั้น*
ไม่เรียกเก็บเงินก่อนทำสัญญาทุกกรณี
ดอกเบี้ยเริ่มต้น 1.5%
วงเงินสูง 5 ล้านบาท
✅หากคุณสนใจบริการของเราโทรด่วนหาเรา
LINE esc.credit
โทร 082 5928519 คุณเอก
โทร 063 2543219 คุณตะวัน
เราพร้อมสนับสนุนธุรกิจคุณ อย่างมั่นคง
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110968
--- Comment #1 from Jonathan Wakely ---
Oh dear, I must have broken this function at some point while implementing
std::format:
// Locale-specific format.
basic_string<_CharT>
_M_localize(basic_string_view<_CharT> __str, char
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110962
--- Comment #1 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:da7b43fb0224cdce5157a747fdd6975b7c81c6cf
commit r14-3126-gda7b43fb0224cdce5157a747fdd6975b7c81c6cf
Author: Juzhe-Zhong
Date: Thu Aug 10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110968
--- Comment #2 from Jonathan Wakely ---
--- a/libstdc++-v3/include/std/format
+++ b/libstdc++-v3/include/std/format
@@ -1634,7 +1634,8 @@ namespace __format
__wstr = _M_localize(__str, __expc, __fc.locale());
else
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110972
Bug ID: 110972
Summary: 13% fatigue regression between g:bb3ceeb6520c13fc
(2023-08-07 21:09) and g:d9dc70cc65becca9 (2023-08-08
13:30)
Product: gcc
Version: 13.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110972
--- Comment #1 from Jan Hubicka ---
The following patches in the range looks like they may cause the difference
commit d9f3ea61fe36e2de3354b90b65ff8245099114c9
Author: Richard Biener
Date: Mon Aug 7 14:44:20 2023 +0200
tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110960
--- Comment #6 from John Platts ---
Need to use revision ff1ad85a96c0bc8483b582d6dbceb8bc07edd226 of Google Highway
to reproduce the PPC9 codegen bug with GCC 12 as the TestSatWidenMulPairwiseAdd
will now pass on PPC9 due to a recent update to T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955
--- Comment #11 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #10 from ro at CeBiTec dot Uni-Bielefeld.DE Uni-Bielefeld.DE> ---
>> --- Comment #9 from Petr Sumbera ---
>> (In reply to r...@cebitec.uni-bielefeld.de from comment #8)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955
--- Comment #12 from Petr Sumbera ---
(In reply to Petr Sumbera from comment #9)
> (In reply to r...@cebitec.uni-bielefeld.de from comment #8)
> > > without the JIT patch (033-solaris-LLVM-JIT.patch)? It may be worth a try
> > > until someone f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108835
Gaius Mulley changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955
--- Comment #13 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #12 from Petr Sumbera ---
> (In reply to Petr Sumbera from comment #9)
>> (In reply to r...@cebitec.uni-bielefeld.de from comment #8)
>> > > without the JIT patch (033-so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110779
--- Comment #12 from Gaius Mulley ---
Created attachment 55717
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55717&action=edit
Another patch for Darwin
More portability configure checks and fixes to wrapclock.cc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110973
Bug ID: 110973
Summary: 9% namd regression between g:c2a447d840476dbd
(2023-08-03 18:47) and g:73da34a538ddc2ad (2023-08-09
20:17)
Product: gcc
Version: 13.1.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110974
Bug ID: 110974
Summary: format out of bounds read on invalid format string
"{:{}."
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110974
--- Comment #1 from Paul Dreik ---
This is very similar to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110862
which has already been fixed on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #94 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:8afe9d5d2fdd047cbd4e3531170af6b66d30e74a
commit r14-3128-g8afe9d5d2fdd047cbd4e3531170af6b66d30e74a
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110975
Bug ID: 110975
Summary: Missed unlooping
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106293
Jan Hubicka changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110975
Jan Hubicka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110976
Bug ID: 110976
Summary: Cryptic error message when incorrectly dereferencing a
pointer in an anonymous union
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110977
Bug ID: 110977
Summary: Should -fms-extensions define _MSC_EXTENSIONS?
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110976
Marek Polacek changed:
What|Removed |Added
Keywords||diagnostic
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110977
Andrew Pinski changed:
What|Removed |Added
Component|c |c++
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #58 from Ed Catmur ---
(In reply to Roman Krotov from comment #57)
> But I don't see any reasons not to implement the switch right now...
Making [[gnu::warn_unused_result]] mean the same as [[nodiscard]] would be a
reduction in expres
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110977
--- Comment #2 from Aaron Ballman ---
(In reply to Andrew Pinski from comment #1)
> I don't think GCC has all of MSVC extensions implemented so defining that
> might break code
Clang doesn't either, FWIW. But the point is well-taken; code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110954
--- Comment #5 from Andrew Pinski ---
Created attachment 55718
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55718&action=edit
new patch which I am testing
The only thing is it is sometimes overly conserative with the check of
`!wascmp |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110971
Andrew Pinski changed:
What|Removed |Added
Summary|ICE on valid code at -O3 on |[14 Regression] ICE on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110923
--- Comment #1 from Andrew Pinski ---
Note PR 110971 might contain a reduced testcase ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110978
Bug ID: 110978
Summary: [14 Regression] ICE lambda constrained with
to-be-deduced object
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: ice-on-invali
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653
John David Anglin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103459
Eric Gallager changed:
What|Removed |Added
CC||arsen at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110976
--- Comment #1 from Andrew Pinski ---
U here stands for unique as in UID. Yes it should not be exposed to the user.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110978
Andrew Pinski changed:
What|Removed |Added
Known to fail||12.3.0
Summary|[14 Regressio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110978
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106852
Jonathan Wakely changed:
What|Removed |Added
See Also||https://github.com/microsof
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110971
--- Comment #1 from Jan Hubicka ---
The problem here is that the split conditional is predicted with probability 0:
if (b.0_1 > a.4_14)
goto ; [0.00%]
else
goto ; [100.00%]
this is caused by jump threading;
[local count: 118111
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110974
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110131
--- Comment #7 from Andrew Pinski ---
(In reply to Andrew Macleod from comment #6)
> poking around for a minute, it looks like simplify_using_ranges from
> vr_values calls a routine called test_for_singularity which has never been
> converted to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110923
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:39204ae9ddbfca710880d7f5fda48234a1e85e4e
commit r14-3133-g39204ae9ddbfca710880d7f5fda48234a1e85e4e
Author: Jan Hubicka
Date: Fri A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110970
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:9cb2a7c8d54b1f6685bc509a07104c458262cb9f
commit r14-3134-g9cb2a7c8d54b1f6685bc509a07104c458262cb9f
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110968
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f48a5423964f72e2e1ba0ad6a14d9d1464a78bed
commit r14-3135-gf48a5423964f72e2e1ba0ad6a14d9d1464a78bed
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110974
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:ecfd8c7ffecf9e8f851c996ec149fbda7ef202f5
commit r14-3136-gecfd8c7ffecf9e8f851c996ec149fbda7ef202f5
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110974
--- Comment #4 from Jonathan Wakely ---
(In reply to CVS Commits from comment #3)
> * include/std/format (_Spec::_S_parse_width_or_precision): Check
> for empty range before dereferencing iterator.
Oops, I fixed it in _M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107687
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954
--- Comment #4 from Romain Geissler ---
In the latest agenda published
(https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3156.pdf) it seems that now
the next C revision has been delayed a bit.
At this point, is it known already if it will be o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66940
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110974
--- Comment #5 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:6ac826917de970ebc789a5a1928d6d6987d85c0b
commit r13-7707-g6ac826917de970ebc789a5a1928d6d6987d85c0b
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110968
--- Comment #4 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:15b3fc6c1c5296662d0ffd7d3cfb8b669421e5ea
commit r13-7706-g15b3fc6c1c5296662d0ffd7d3cfb8b669421e5ea
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110974
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110968
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105644
--- Comment #2 from Namniav ---
Now Clang also crashes on the original
example(https://github.com/llvm/llvm-project/issues/64607), although its cause
may be different to GCC's.
I can't remember why I used `get` instead of `std::get` in original
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637
--- Comment #7 from Andrew Pinski ---
(In reply to Andrew Macleod from comment #2)
>
> Why are we adding -1 to [0,3] ? Thats the root of this issue I think?
> seems strange
if we ignore the range for a second.
When switch conversion happens
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110979
Bug ID: 110979
Summary: Miss-optimization for O2 fully masked loop on floating
point reduction.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110980
Bug ID: 110980
Summary: -flang-info-include-translate does not work with no
argument
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 110 matches
Mail list logo
