https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120450
Bug ID: 120450
Summary: GCN offloading: ICE 'during RTL pass: expand', 'in
assign_temp, at function.cc:990' for C++
'std::flat_map', 'std::flat_multimap'
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120428
--- Comment #15 from Jonathan Wakely ---
(In reply to Hongtao Liu from comment #13)
> The inner loop is not completely unrolled since std::copy is lowered to
> __builtin_memmove instead of __builtin_memcpy
std::copy allows the end of the output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117785
--- Comment #17 from Hana Dusíková ---
(In reply to Jakub Jelinek from comment #16)
> So, the paper added also the new case to
> https://eel.is/c++draft/expr.const#10.27
> but
> https://eel.is/c++draft/expr.new#8.5
> has not been changed and sti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120440
--- Comment #6 from Eric Botcazou ---
> It bisects to r15-8901-g7bec4570301c43 which I find very surprising. Double
> checked with a build of r15-8900-g525d4a10302113 (which works) and
> r15-8901-g7bec4570301c43 (which doesn't).
This patch does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
--- Comment #10 from Francois-Xavier Coudert ---
> It would be much nicer if we could do something more like other places
> in the compiler, where there is some script to run in the source directory
> that can be done when one changes the m4 (an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120447
--- Comment #2 from Andrew Pinski ---
Created attachment 61530
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61530&action=edit
`-mcpu=neoverse-v2 -Ofast` is enough with this one
This is a better reduced testcase that fails even without l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117025
--- Comment #10 from Haochen Jiang ---
Fixed that texi issue for now by committing the patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120448
--- Comment #2 from Richard Biener ---
-fuse-ld is deeply flawed - all configure time checks on linker features are
for the wrong linker then. We need to get rid of those to make it sound.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
--- Comment #9 from Iain Sandoe ---
If the Fortran maintainers prefer to revert the patch then I shall not
complain.
The configure version was changed in GCC-9 and no-one had stepped forward to
update the Fortran build code even by GCC-15. I (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116809
--- Comment #34 from GCC Commits ---
The releases/gcc-13 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:3599245e4972b2322f75c909bc81961e41bc64ad
commit r13-9719-g3599245e4972b2322f75c909bc81961e41bc64ad
Author: Mark Mentovai
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119172
--- Comment #5 from GCC Commits ---
The releases/gcc-13 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:d9cd8d7babe838b577c6ede08589a79bb3df7810
commit r13-9721-gd9cd8d7babe838b577c6ede08589a79bb3df7810
Author: Iain Sandoe
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120447
Tamar Christina changed:
What|Removed |Added
Status|WAITING |NEW
Keywords|needs-source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117785
--- Comment #16 from Jakub Jelinek ---
So, the paper added also the new case to
https://eel.is/c++draft/expr.const#10.27
but
https://eel.is/c++draft/expr.new#8.5
has not been changed and still says that say new int[-1] in constexpr function
is i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120447
Andrew Pinski changed:
What|Removed |Added
Attachment #61530|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117785
--- Comment #18 from Hana Dusíková ---
(In reply to Jakub Jelinek from comment #16)
> So, the paper added also the new case to
> https://eel.is/c++draft/expr.const#10.27
> but
> https://eel.is/c++draft/expr.new#8.5
> has not been changed and sti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120032
--- Comment #4 from Richard Biener ---
I'll also note that as written the table-based lookup has a value of 31 for
zero input but lzcnt will get you 32. So unless you make the input of zero
undefined by guarding the code (thus provide a value-r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120451
Bug ID: 120451
Summary: CSWTCH variables should be mergable
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120451
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
--- Comment #11 from Jonathan Wakely ---
(In reply to Francois-Xavier Coudert from comment #10)
> I'd rather have a script like libgfortran/regenerate.sh, that calls m4 and
> updates the tree. Then maintainers know that, if they changed any m4 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120451
--- Comment #2 from Andrew Pinski ---
Oh DECL_MERGEABLE was only added recently in GCC 14 by
r14-1500-g4d935f52b0d5c0. This might be the reason why it was not marked as
CSWTCH was added in r0-92923-g7156c8abaf8f39 (4.5).
own-linux-gnu-as --disable-multilib
--enable-libsanitizer --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-20250528154756-r16-937-g0f73ae763c02ad-checking-yes-rtl-df-extra-riscv64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 16.0.0 20250528 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120462
Bug ID: 120462
Summary: install.texi missing --enable-checking flag
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856
--- Comment #4 from Jerry DeLisle ---
Note: I biffed the PR number in the log.
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:e2bf0b3910de7e65363435f0a7fa606e2448a677
commit r16-939-ge2bf0b3910de7e65363435f0a7fa60
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120463
Bug ID: 120463
Summary: Pb Doubled linked List
Product: gcc
Version: 13.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282
Jerry DeLisle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856
Jerry DeLisle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856
Bug 119856 depends on bug 83282, which changed state.
Bug 83282 Summary: missing comma in format changes output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120464
Bug ID: 120464
Summary: Build broken in ggc-page.cc on master
Product: gcc
Version: 15.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120464
--- Comment #1 from Zartaj Majeed ---
The build error is
g++ -std=c++14 -fno-PIE -c -g -DIN_GCC-fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-error=narrowing -Wwrite-strings
-Wcast-qual -Wno-format -Wmissing-format-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #21 from GCC Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:e8fdd55ec907496ff3c80fed55d8da3ddbdc1a2b
commit r16-938-ge8fdd55ec907496ff3c80fed55d8da3ddbdc1a2b
Author: Yuao Ma
Date: Wed May
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119586
--- Comment #8 from GCC Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:e2bf0b3910de7e65363435f0a7fa606e2448a677
commit r16-939-ge2bf0b3910de7e65363435f0a7fa606e2448a677
Author: Jerry DeLisle
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110634
--- Comment #7 from Vineet Gupta ---
As of gcc-15.1 release, ra is being stored and both gcc and llvm seem to be
generate compatible code.
https://godbolt.org/z/jze1TMKbW
foo:
addisp,sp,-16
sd s0,0(sp)
sd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119586
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120464
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
--- Comment #12 from Francois-Xavier Coudert ---
Created attachment 61532
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61532&action=edit
Regeneration script
Attached is a shell script, to be placed in libgfortran/, that can be run in
th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99015
--- Comment #12 from Vladimir Makarov ---
Created attachment 61535
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61535&action=edit
A candidate patch for gcc-13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99015
--- Comment #13 from Vladimir Makarov ---
(In reply to Jakub Jelinek from comment #11)
> r14-7141-ga729b6e002fe76208f33fdcdee49d6a310a1940e fixed it.
The patch needed some reworking for gcc-13 as there were changes in the same
code parts.
I am
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71713
Zdenek Sojka changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment #3 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120450
--- Comment #1 from Richard Biener ---
The question is what's the reason we end up here from expand_constructor.
There's
/* Handle calls that pass values in multiple non-contiguous
locations. The Irix 6 ABI has examples of this. */
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
Sam James changed:
What|Removed |Added
Keywords||rejects-valid
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #2 from Sam James ---
Created attachment 61534
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61534&action=edit
partial.cpp.ii.xz
Attaching a partial reduction, still running, but it's slow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120454
Bug ID: 120454
Summary: C++ constexpr vs. OpenMP implicit mapping
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: openmp
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118694
--- Comment #13 from GCC Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:5b2e7afb135aa10e17e51b891d4b2c85ee541ade
commit r16-935-g5b2e7afb135aa10e17e51b891d4b2c85ee541ade
Author: Tobias Burnus
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120436
Robin Dapp changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99832
--- Comment #13 from dave.anglin at bell dot net ---
If you have a proposed patch, I'm willing to test.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #5 from Iain Sandoe ---
thanks for the report.
Note that GCC-15 is not doing the correct operations in respect of the CWG2563
discussions (see PR119916 and PR115908).
However, this can still be a new issue (not analysed so far).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120432
--- Comment #4 from Patrick Palka ---
(In reply to Patrick Palka from comment #3)
> (In reply to Arthur O'Dwyer from comment #2)
> > But I think a better answer in this case is "because using
> > a volatile index *will not actually compile*, so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120456
Bug ID: 120456
Summary: __builtin_shuffle produces unnecessary vperm2i128
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #4 from Sam James ---
Created attachment 61538
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61538&action=edit
reduced.ii
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107600
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed|2022-11-10 00:00:00 |2025-5-28
--- Comment #3 from Jonatha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120458
--- Comment #1 from Jonathan Wakely ---
Clang compiles this, and I think MSVC does, but EDG doesn't (but EDG also
doesn't accept that identifier for a variable name, at least with the default
options).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
--- Comment #14 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #13)
> (In reply to Francois-Xavier Coudert from comment #12)
> > Created attachment 61532 [details]
> > Regeneration script
> >
> > Attached is a shell script, to be pl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115908
--- Comment #10 from Iain Sandoe ---
my understanding is that the conclusion of CWG2563 is that this behaviour was
not the intended design - and the resolution to this is in PR119916.
(so that, unless there's new information, this bug would be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11234
Andrew Pinski changed:
What|Removed |Added
CC||ssofroni at cytanet dot com.cy
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120452
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120432
--- Comment #6 from Jonathan Wakely ---
Please don't waste time on the volatile question. What does it mean to lookup a
volatile value that could change at any moment? What is the library even
supposed to do with a volatile int& there, read it a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120452
--- Comment #2 from Andrew Pinski ---
Basically don't use -Wpedantic if you don't want any extensions (include
extensions required for POSIX).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109345
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117785
Jakub Jelinek changed:
What|Removed |Added
Attachment #61528|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120460
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2025-05-28
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120460
--- Comment #3 from Jonathan Wakely ---
i.e. maybe this warning should ignore whether it's in a system header or not.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
Iain Sandoe changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #9 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110634
Vineet Gupta changed:
What|Removed |Added
Resolution|--- |FIXED
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120465
Bug ID: 120465
Summary: Incorrect value_type for std::flat_map
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120465
--- Comment #1 from Eligor Kadaf ---
The value_type seems to be as expected: https://godbolt.org/z/MWs531orx
However the example in comment above shall compile, yet it doesn't.
Fun fact is that if we change const auto& pair to const std::pair& p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107600
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #22 from GCC Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:a64a7f0a6cf8afcbad4bd6c9e1b0f1d4f2d5b958
commit r16-940-ga64a7f0a6cf8afcbad4bd6c9e1b0f1d4f2d5b958
Author: Tobias Burnus
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104454
--- Comment #4 from Jonathan Wakely ---
Actually that's wrong because path("foo/bar/..").lexically_normal() is just
"foo" which ignores whether foo/bar is a symlink to somewhere else.
I think the right fix is to just not define _GLIBCXX_USE_REA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #10 from Jason Merrill ---
(In reply to Iain Sandoe from comment #9)
> OK so the reason this fails is because check_return_expr() concludes that we
> cannot do NRVO
Yes, because the implementation is permitted to use temporary objec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120466
Bug ID: 120466
Summary: Analyzer report for C++ 'std::stringbuf' instantiation
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120353
--- Comment #2 from qinzhao at gcc dot gnu.org ---
the following patch fixes the issue:
[opc@qinzhao-aarch64-ol8 c]$ git diff
diff --git a/gcc/c/c-decl.cc b/gcc/c/c-decl.cc
index ad66d7d258b..4733287eaf8 100644
--- a/gcc/c/c-decl.cc
+++ b/gcc/c/c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120467
Bug ID: 120467
Summary: Analyzer: Diagnose cases where C++
'std::basic_string_view::data()' is used as
NUL-terminated string, but isn't
Product: gcc
Version: 16.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120464
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |16.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104454
--- Comment #5 from Jonathan Wakely ---
I did try this:
--- a/libstdc++-v3/src/c++17/fs_ops.cc
+++ b/libstdc++-v3/src/c++17/fs_ops.cc
@@ -164,6 +164,21 @@ fs::canonical(const path& p, error_code& ec)
path result;
#ifdef _GLIBCXX_FILESYSTEM_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120465
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
Status|UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120465
--- Comment #3 from Jonathan Wakely ---
(In reply to Eligor Kadaf from comment #0)
> However, it seems that in libstdc++ implementation of std::flat_map it's
> value_type is std::tuple.
No, the predicate is just called on the elements of a zip_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104454
--- Comment #6 from Jonathan Wakely ---
See also https://lists.gnu.org/archive/html/bug-make/2025-05/msg2.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431
--- Comment #7 from kargls at comcast dot net ---
Created attachment 61543
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61543&action=edit
Fix for scalar source with ncopies < 0
This patch fixes the case of a scalar SOURCE and NCOPIES < 0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #7 from Iain Sandoe ---
(In reply to Andrew Pinski from comment #6)
> Interesting if I change the lambda into a normal function:
> ```
> auto coro() ->LazyTask
> {
> co_await []() -> Task {}();
> }
> ```
>
> GCC 15 rejects i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68612
Andrew Pinski changed:
What|Removed |Added
CC||lavr at ncbi dot nlm.nih.gov
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
Iain Sandoe changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
--- Comment #5 from lavr at ncbi dot nlm.nih.gov ---
Wow, it's a ten year old problem now is breaking the builds because of the
warning to error promotion! The latter should not have been done with the
outstanding problem like that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
--- Comment #6 from Sam James ---
(In reply to lavr from comment #5)
> Wow, it's a ten year old problem now is breaking the builds because of the
> warning to error promotion! The latter should not have been done with the
> outstanding problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68612
--- Comment #9 from lavr at ncbi dot nlm.nih.gov ---
GCC14 is breaking builds now, because the warning has been promoted to error,
with this problem still unresolved.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
--- Comment #7 from lavr at ncbi dot nlm.nih.gov ---
> it would be an *extension*.
An extension to what? Other compilers allow the const qualifier conversion,
and it's logically correct (and it is correct in C++, like shown).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104454
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104454
--- Comment #3 from Jonathan Wakely ---
This fixes the FAIL for 27_io/filesystem/operations/weakly_canonical.cc
--- a/libstdc++-v3/src/c++17/fs_ops.cc
+++ b/libstdc++-v3/src/c++17/fs_ops.cc
@@ -162,7 +162,7 @@ fs::path
fs::canonical(const path
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
--- Comment #13 from Iain Sandoe ---
(In reply to Francois-Xavier Coudert from comment #12)
> Created attachment 61532 [details]
> Regeneration script
>
> Attached is a shell script, to be placed in libgfortran/, that can be run in
> that direc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120432
--- Comment #3 from Patrick Palka ---
(In reply to Arthur O'Dwyer from comment #2)
> But I think a better answer in this case is "because using
> a volatile index *will not actually compile*, so flat_map shouldn't
> gratuitously advertise that s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99832
--- Comment #12 from Jonathan Wakely ---
Also, I don't think we need the abi tag from from_time_t, because the mangled
name of that function already depends on the type of time_t. The problem with
to_time_t is that the mangled name does not depen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120450
Richard Biener changed:
What|Removed |Added
Keywords||needs-reduction
--- Comment #2 from Ri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118694
--- Comment #14 from GCC Commits ---
The releases/gcc-15 branch has been updated by Tobias Burnus
:
https://gcc.gnu.org/g:c38760cdb2ac21f690647e965acc0eaba3250f6d
commit r15-9740-gc38760cdb2ac21f690647e965acc0eaba3250f6d
Author: Tobias Burnus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
--- Comment #1 from Sam James ---
https://x.com/__phantomderp/status/1804967387864691052
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #6 from Andrew Pinski ---
Interesting if I change the lambda into a normal function:
```
auto coro() ->LazyTask
{
co_await []() -> Task {}();
}
```
GCC 15 rejects it and then ICEs:
```
: In function 'QCoro::LazyTask QCoro::c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120432
--- Comment #5 from Arthur O'Dwyer ---
> I think this also means the standard transparent-compare overload is
> underconstrained [...] m[k] for volatile k is a soft/constraint error if
the comparator is non-transparent, but is a hard error if t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120452
Bug ID: 120452
Summary: error: ISO C forbids conversion of function pointer to
object pointer type
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93226
Tobias Burnus changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
Bug ID: 120453
Summary: [16 regression] qcoro fails to build its tests
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
Bug ID: 120455
Summary: char** and -Wincompatible-pointer-types
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
1 - 100 of 139 matches
Mail list logo
