https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120449
--- Comment #8 from Andrew Pinski ---
(In reply to Zartaj Majeed from comment #6)
> Underline is wrong and confusing with --save-temps
Don't use -save-temps if you want decent diagnostic/column info.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120449
--- Comment #7 from Zartaj Majeed ---
Should I open a separate bug for libstdc++ for the warning?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120449
--- Comment #6 from Zartaj Majeed ---
Thanks - the following works
diff --git a/gcc/c-family/c-common.cc b/gcc/c-family/c-common.cc
index f71cb2652d5..6d7ef006c6a 100644
--- a/gcc/c-family/c-common.cc
+++ b/gcc/c-family/c-common.cc
@@ -3318,7 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:bd9d8f9b294d9aef8799227234bd09e26a9a6640
commit r16-948-gbd9d8f9b294d9aef8799227234bd09e26a9a6640
Author: Jerry DeLisle
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #13 from Jason Merrill ---
In the original testcase we do choose to do NRVO, but this fails
/* Don't check copy-initialization for NRV in a coroutine ramp; we
implement this case as NRV, but it's specified as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #12 from Jason Merrill ---
(In reply to Iain Sandoe from comment #11)
Good point, in the reduced testcase, under
https://eel.is/c++draft/class.mem#class.copy.ctor-8 TaskBase doesn't get a move
constructor at all. But in the origina
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107600
Jason Merrill changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107600
--- Comment #4 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:0629924777ea20d56d9ea40c3915eb0327a22ac7
commit r16-944-g0629924777ea20d56d9ea40c3915eb0327a22ac7
Author: Jason Merrill
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120428
--- Comment #16 from Hongtao Liu ---
(In reply to Jonathan Wakely from comment #15)
> (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 __built
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120464
--- Comment #6 from Zartaj Majeed ---
Do you mind fixing the "garantee" typo in the last comment too?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120464
--- Comment #5 from Andi Kleen ---
Sorry about that. Thanks Jakub. Patch looks good to me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120468
--- Comment #4 from Andrew Pinski ---
(In reply to James Abbatiello from comment #3)
> Bisecting leads me to
> 7bc63f1c70331763989d72b7df051e0ce67ff84c
> [i386] adjust flag_omit_frame_pointer in a single function [PR113719]
r14-10426 looks like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120468
--- Comment #3 from James Abbatiello ---
Bisecting leads me to
7bc63f1c70331763989d72b7df051e0ce67ff84c
[i386] adjust flag_omit_frame_pointer in a single function [PR113719]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120462
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
--- Comment #11 from Iain Sandoe ---
so... if I add this - non-coroutine ...
LazyTask
foo (detail::LazyTaskPromise& p)
{
decltype(auto) Gro = p.get_return_object();
return Gro;
}
we essentially get the same fail;
../temp-coro-tests/pr1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120468
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120468
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.4
Summary|Inlining fails
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99015
--- Comment #14 from Vladimir Makarov ---
(In reply to Vladimir Makarov from comment #13)
> I am putting a candidate patch in the attachment. I'll approve it after
> finishing tests and bootstraps on amd64, arm64, ppc64.
The patch testing seem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120468
Bug ID: 120468
Summary: Inlining fails when using -momit-leaf-frame-pointer,
optimize attribute, and push_options pragma
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119298
--- Comment #21 from GCC Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:8859a06fc8143561dd94ef2342234dbc5ccfd937
commit r16-941-g8859a06fc8143561dd94ef2342234dbc5ccfd937
Author: Jan Hubicka
Date: Wed M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120464
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
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=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=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=120465
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
Status|UNCO
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=120464
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |16.0
Priority|P3
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=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=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=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=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=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=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=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=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=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=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=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=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=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=83282
Jerry DeLisle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
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=119586
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Commen
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=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=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=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
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=116400
--- Comment #15 from kargls at comcast dot net ---
(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
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=104454
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
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=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 #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=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=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
--- 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=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=120460
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2025-05-28
Ever confirmed|0
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=109345
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Commen
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=120452
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
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=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=120456
--- Comment #3 from Andrew Pinski ---
Options: `-Ofast -mavx2 -std=c++23`.
Next time please attach the compilable testcase (or place it inline) and not
just a code snip. Also add the options you are using.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109345
--- Comment #14 from Paul Thomas ---
(In reply to Paul Thomas from comment #13)
> I have had a period of not being able to work on gfortran. I'll take a look
> at this today.
Some other patch has been applied to 14-branch onwards that results
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120456
--- Comment #2 from Andrew Pinski ---
Created attachment 61539
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61539&action=edit
Full testcase
++ |c++
--- Comment #1 from Andrew Pinski ---
With -Wsystem-headers, I get:
```
/opt/compiler-explorer/arm64/gcc-trunk-20250528/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/include/c++/16.0.0/bits/invoke.h:113:35:
warning: ignoring returned value of type 'A', dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120460
Bug ID: 120460
Summary: std::function ignores [[nodiscard]] attribute
Product: gcc
Version: 15.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65608
Bug 65608 depends on bug 119378, which changed state.
Bug 119378 Summary: [12/13 Regression] Nested template class friend of template
class produces "internal compiler error: unexpected expression âTâ of kind
template_parm_index"
https://gcc.gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119378
Patrick Palka changed:
What|Removed |Added
Target Milestone|12.5|14.3
Status|ASSIGNED
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=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=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=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=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=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=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=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=120459
Bug ID: 120459
Summary: RISC-V: redundant addi
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assign
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120458
Bug ID: 120458
Summary: module-name does not allow non-ASCII characters
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120456
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99832
--- Comment #14 from Jonathan Wakely ---
Created attachment 61536
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61536&action=edit
Add abi tag to system_clock::to_time_t
Here's a new patch, which includes a test to verify that the abi_tag
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
--- Comment #3 from lavr at ncbi dot nlm.nih.gov ---
* was prompted
was promoted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
--- Comment #21 from GCC Commits ---
The releases/gcc-13 branch has been updated by Martin Jambor
:
https://gcc.gnu.org/g:a067a18d42e338aea990347bb4d16d6a852c4480
commit r13-9724-ga067a18d42e338aea990347bb4d16d6a852c4480
Author: Martin Jambor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120455
--- Comment #2 from lavr at ncbi dot nlm.nih.gov ---
sja...@gcc.gnu.org:
Strictly speaking, returning a pointer is not the same as taking it in by
adding const qualifiers. In my code example, "func()" can't change anything
pointed to by "str",
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120453
Sam James changed:
What|Removed |Added
Summary|[16 regression] qcoro fails |[16 regression] qcoro fails
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120457
Bug ID: 120457
Summary: gcc.dg/vect/pr79920.c fail starting with
r16-924-g1bc5b47f5b06dc
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: testsuite-fai
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=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=120436
Robin Dapp changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120436
--- Comment #1 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:6ccf845d9fa157e7ebcf2c589a9fc5d8f298961f
commit r16-936-g6ccf845d9fa157e7ebcf2c589a9fc5d8f298961f
Author: Robin Dapp
Date: Mon May
1 - 100 of 139 matches
Mail list logo
