https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119286
--- Comment #8 from Thomas Schwinge ---
Tamar, thanks! I confirm all fixed -- but one:
(In reply to myself from comment #1)
> ..., and similarly -- but not identical! -- for '-march=gfx1100':
> PASS: gcc.dg/vect/vect-early-break_38.c (tes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119858
Tamar Christina changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119818
Thomas Schwinge changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119160
--- Comment #6 from GCC Commits ---
The trunk branch has been updated by Philipp Tomsich :
https://gcc.gnu.org/g:7e628ff49f7f890d5337369d7b4f8e21a1f17029
commit r16-15-g7e628ff49f7f890d5337369d7b4f8e21a1f17029
Author: kelefth
Date: Thu Mar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119840
--- Comment #4 from Tomasz Kamiński ---
I would like to get confirmation from John David Anglin, that warnings no
longer appear on the target.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836
--- Comment #11 from anlauf at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #10)
> Hi Folks,
>
> Is it worth reverting or fixing this before the 15-branch release? After
> all, the bug made its way into the Fedora 42 release?
>
> C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119858
Bug ID: 119858
Summary: [15/16 Regression] GCN vs. "middle-end: Fix incorrect
codegen with PFA and VLS [PR119351]"
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119857
Bug ID: 119857
Summary: GCN offloading: occasional
'libgomp.c-c++-common/declare-target-indirect-2.c'
execution test FAIL
Product: gcc
Version: 15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119286
--- Comment #9 from Tamar Christina ---
(In reply to Thomas Schwinge from comment #8)
> Tamar, thanks! I confirm all fixed -- but one:
>
> (In reply to myself from comment #1)
> > ..., and similarly -- but not identical! -- for '-march=gfx1100
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119858
--- Comment #2 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:1f7ac78efa622e19f38d6a45e857941b3dea1437
commit r16-19-g1f7ac78efa622e19f38d6a45e857941b3dea1437
Author: Richard Biener
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119858
--- Comment #3 from GCC Commits ---
The releases/gcc-15 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:d88b917325546cee24a544dc05cbfbef0febfe25
commit r15-9557-gd88b917325546cee24a544dc05cbfbef0febfe25
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836
--- Comment #12 from kargls at comcast dot net ---
On 4/17/25 23:59, pault at gcc dot gnu.org wrote:
>
> Is it worth reverting or fixing this before the 15-branch release? After all,
> the bug made its way into the Fedora 42 release?
I'll submi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
Andrew Pinski changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
Patrick Palka changed:
What|Removed |Added
CC||jason at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
--- Comment #2 from Andrew Pinski ---
Another example:
```
struct A {
template
const A& f();
const A& g();
};
struct B : public A {
using A::f;
using A::g;
template
const int f();
const int g();
};
int main() {
B b;
b.g();
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119861
Bug ID: 119861
Summary: formatter specialization of formatter for map class
scope has set_separator/set_brackets
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119861
--- Comment #1 from 康桓瑋 ---
..which should not:
#include
struct Map {
std::pair* begin();
std::pair* end();
};
template<>
constexpr auto std::format_kind = std::range_format::map;
int main() {
std::formatter fmt;
fmt.set_separator("
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836
--- Comment #13 from Jerry DeLisle ---
(In reply to kargls from comment #12)
> On 4/17/25 23:59, pault at gcc dot gnu.org wrote:
> >
> > Is it worth reverting or fixing this before the 15-branch release? After
> > all,
> > the bug made its way
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119862
Bug ID: 119862
Summary: gcc.dg/pr119160.c FAILs
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
--- Comment #3 from Andrew Pinski ---
Another example:
```
struct A {
template
const A& f(T);
const A& g(int);
template
const A& h();
};
struct B : public A {
using A::f;
using A::g;
using A::h;
template
const int f(T);
co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119862
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |16.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
--- Comment #4 from Jason Merrill ---
(In reply to Andrew Pinski from comment #2)
> GCC trunk seemly only rejects the template member function as being
> ambigious though.
Yes, because https://eel.is/c++draft/namespace.udecl#11 says "The set of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
--- Comment #5 from Jason Merrill ---
(In reply to Andrew Pinski from comment #3)
> Another example:
...
> template
> const A& h();
...
> b.h();
T cannot be deduced in this call, so A::h is not a viable candidate, so it's
not ambiguous.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836
Paul Thomas changed:
What|Removed |Added
CC||pault at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119818
--- Comment #2 from GCC Commits ---
The trunk branch has been updated by Thomas Schwinge :
https://gcc.gnu.org/g:ed8761241ac529ccddb2b76a1895c124c67c132c
commit r16-30-ged8761241ac529ccddb2b76a1895c124c67c132c
Author: Thomas Schwinge
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119502
Jerry DeLisle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836
--- Comment #15 from Jerry DeLisle ---
Building with Steve's latest patch now. If all passes here I will commit to 16
and request to backport to 15. Thanks Steve.
-linux-gnu
Configurado con: ../gcc-15.1.0-RC-20250418/configure --disable-multilib
--disable-bootstrap --enable-languages=c,c++ --prefix=/home/pililatiesa/gcc-15/
Modelo de hilos: posix
Algoritmos de compresión LTO admitidos: zlib zstd
gcc versión 15.0.1 20250418 (prerelease) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119865
Bug ID: 119865
Summary: [15/16 regression] RISC-V: ICE in
g++.target/riscv/mv(c)-symbols[1-5].C
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
Bug ID: 119867
Summary: Spurious warning about out-of-bound write with -O3 and
-D_GLIBCXX_ASSERTIONS
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
Yichao Yu changed:
What|Removed |Added
Blocks|88443 |
Component|tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836
--- Comment #14 from kargls at comcast dot net ---
Created attachment 61157
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61157&action=edit
Patch to fix issue
Here are Changelog entries for fortran/ and testsuite/.
2025-04-18 Steven G.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
Andrew Pinski changed:
What|Removed |Added
Blocks||88443
--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
--- Comment #3 from Andrew Pinski ---
There might be another dup of this bug too ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119840
John David Anglin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119858
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108016
--- Comment #10 from GCC Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:529a43109fcd93f5aafda345da14679f538ada86
commit r16-17-g529a43109fcd93f5aafda345da14679f538ada86
Author: Alexey Merzlyakov
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119351
Bug 119351 depends on bug 119858, which changed state.
Bug 119858 Summary: [15/16 Regression] GCN vs. "middle-end: Fix incorrect
codegen with PFA and VLS [PR119351]"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119858
What|Remove
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119858
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119860
Bug ID: 119860
Summary: needless vector unrolling causes less profitable
vectorization
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: missed-optim
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
--- Comment #8 from Andrew Pinski ---
(In reply to Yichao Yu from comment #5)
> Yeah adding explicit bounds check do work but I still don't think the
> compiler should be warning about this type of possible out-of-bound access.
The problem is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80328
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
--- Comment #5 from Yichao Yu ---
Yeah adding explicit bounds check do work but I still don't think the compiler
should be warning about this type of possible out-of-bound access.
FWIW, this code originate from a bigger project where the bounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
--- Comment #4 from Andrew Pinski ---
(In reply to Yichao Yu from comment #1)
> As a meta bug, should the ''result_decl' not supported by
> dump_expr' in the error message be reported anywhere? Both
> the fact that it couldn't print and that it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
--- Comment #6 from Yichao Yu ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Yichao Yu from comment #1)
> > As a meta bug, should the ''result_decl' not supported by
> > dump_expr' in the error message be reported anywhere? Both
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119868
Bug ID: 119868
Summary: `'result_decl' not supported by dump_expr` is printed instead of ` res` in
some cases
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Ke
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119867
--- Comment #7 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Yichao Yu from comment #1)
> > As a meta bug, should the ''result_decl' not supported by
> > dump_expr' in the error message be reported anywhere? B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119859
Bug ID: 119859
Summary: [15 Regression?] template member function overload
with base class
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
ión de segmento
8 | T s = sum(v, 3u);
| ^~~
0x22373d6 internal_error(char const*, ...)
../../gcc-15.1.0-RC-20250418/gcc/diagnostic-global-context.cc:517
0xf8a223 crash_signal
../../gcc-15.1.0-RC-20250418/gcc/toplev.cc:322
0x77463624532f ???
./signal/../sy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83022
--- Comment #18 from Andrew Pinski ---
Created attachment 61156
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61156&action=edit
Full patch which I will be submitting once testing is finished
It does not do the probability but does handle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119836
--- Comment #16 from GCC Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:f9ea46d946887a05d7ecbca5aeeb99fd868f6e70
commit r16-32-gf9ea46d946887a05d7ecbca5aeeb99fd868f6e70
Author: Steven G. Kargl
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119863
Nathaniel Shead changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119863
Nathaniel Shead changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110522
--- Comment #6 from Roman Lebedev ---
Somewhat relevant: i've looked into feeding such compiler SARIF's
into already-existing Github SARIF upload tooling, and it almost works,
consider upvoting: https://github.com/orgs/community/discussions/1571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83022
--- Comment #19 from Andrew Pinski ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2025-April/681439.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44677
--- Comment #19 from Vincent Lefèvre ---
(In reply to Andrew Pinski from comment #18)
> *** Bug 119544 has been marked as a duplicate of this bug. ***
The example in this bug was
extern char* str;
void foo(void)
{
int i = 0;
while (*s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47781
Luke Shumaker changed:
What|Removed |Added
CC||lukeshu at lukeshu dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119865
Sam James changed:
What|Removed |Added
Target Milestone|--- |15.0
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119865
Sam James changed:
What|Removed |Added
Keywords||ice-on-valid-code
--- Comment #1 from Sam J
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119160
Sam James changed:
What|Removed |Added
Target Milestone|--- |16.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119507
Sam James changed:
What|Removed |Added
Keywords||patch
--- Comment #7 from Sam James ---
(I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119869
Bug ID: 119869
Summary: copysign(0, x) code could be better
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119291
--- Comment #19 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:7381ea8fc4d6dc12af287c20caa3b2019b2f6567
commit r14-11653-g7381ea8fc4d6dc12af287c20caa3b2019b2f6567
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119582
--- Comment #5 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:c0946fe4d216829e96bf2cd64faf5e4630dd8cc2
commit r14-11654-gc0946fe4d216829e96bf2cd64faf5e4630dd8cc2
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101075
--- Comment #4 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:50bd360f9270e6656368a5bdf9426b4022780609
commit r14-11663-g50bd360f9270e6656368a5bdf9426b4022780609
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119722
--- Comment #6 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:056a01f9fa85c584ed97533e75b50160d5993613
commit r14-11658-g056a01f9fa85c584ed97533e75b50160d5993613
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119808
--- Comment #8 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:40c50659569f9d50db9108a5a9847518a5bcec66
commit r14-11662-g40c50659569f9d50db9108a5a9847518a5bcec66
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119707
--- Comment #7 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:008ba21711a4aef3b6d6e7d3dbbe2f2265e29ff8
commit r14-11657-g008ba21711a4aef3b6d6e7d3dbbe2f2265e29ff8
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119785
--- Comment #8 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:efb22612f98c79f38c9e9c7ace3bc681dbcecc03
commit r14-11661-gefb22612f98c79f38c9e9c7ace3bc681dbcecc03
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119625
--- Comment #7 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:293a95b87c5676ff04c6511e900c3d127692d664
commit r14-11655-g293a95b87c5676ff04c6511e900c3d127692d664
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101075
--- Comment #5 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:d490c5884bf0e5b8d8752969d2ee4dacea700be0
commit r14-11664-gd490c5884bf0e5b8d8752969d2ee4dacea700be0
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119727
--- Comment #9 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:438c4df22217280df3f141bd0b1df0523b4de6d3
commit r14-11660-g438c4df22217280df3f141bd0b1df0523b4de6d3
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119727
--- Comment #8 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:2aa812386ad5950283f800257c37bdb78691e770
commit r14-11659-g2aa812386ad5950283f800257c37bdb78691e770
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119796
--- Comment #11 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:50bd360f9270e6656368a5bdf9426b4022780609
commit r14-11663-g50bd360f9270e6656368a5bdf9426b4022780609
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119870
Bug ID: 119870
Summary: `(vector8 unsigned) {0,0x8000}` and `-0.0`
constant formation could be better
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119796
--- Comment #12 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:d490c5884bf0e5b8d8752969d2ee4dacea700be0
commit r14-11664-gd490c5884bf0e5b8d8752969d2ee4dacea700be0
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119871
Bug ID: 119871
Summary: Function parameters should never be name-independent
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: accepts-invalid
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118947
--- Comment #7 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1
commit r16-22-g94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1
Author: Andrew Pinski
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87901
--- Comment #8 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:800b3977031dd4f14d09ced975276e09457dfff7
commit r16-25-g800b3977031dd4f14d09ced975276e09457dfff7
Author: Andrew Pinski
Date: Mon A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118947
--- Comment #8 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:7b4849ec79873fa6de98436deda47e19cbac32ef
commit r16-23-g7b4849ec79873fa6de98436deda47e19cbac32ef
Author: Andrew Pinski
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87901
--- Comment #9 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:2d693c1ffd849e0c1df9cc6610a69a63ffcb2956
commit r16-26-g2d693c1ffd849e0c1df9cc6610a69a63ffcb2956
Author: Andrew Pinski
Date: Mon A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36602
Bug 36602 depends on bug 87901, which changed state.
Bug 87901 Summary: partial DSE of memset doesn't work for other kind of stores
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87901
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118947
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87901
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78408
--- Comment #13 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1
commit r16-22-g94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1
Author: Andrew Pinski
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118902
--- Comment #5 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:16082bdc6beef1ca1485ed5ccdc0c52aabbe0f4c
commit r16-24-g16082bdc6beef1ca1485ed5ccdc0c52aabbe0f4c
Author: Andrew Pinski
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118902
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |16.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
Bug ID: 119866
Summary: constant evaluation failure with trivial function
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
--- Comment #1 from Andrew Pinski ---
I am not sure if __builtin_strlen is supposed to be callable from constexpr at
all.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
--- Comment #2 from Andrew Pinski ---
Though __builtin_strlen might not be the issue here...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
--- Comment #3 from Barry Revzin ---
Well even gcc 4.7.1 accepted this
int main() {
static_assert(__builtin_strlen("hi") == 2, "!");
}
At this point lots of code relies on that working.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
--- Comment #5 from Andrew Pinski ---
Created attachment 61155
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61155&action=edit
Reduced testcase without templates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
--- Comment #4 from Andrew Pinski ---
And yes it is due to __builtin_strlen in some cases.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 119866, which changed state.
Bug 119866 Summary: constexpr with __builtin_strlen does not always work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106889
Andrew Pinski changed:
What|Removed |Added
CC||barry.revzin at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119866
--- Comment #7 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #6)
> Dup.
>
> *** This bug has been marked as a duplicate of bug 106889 ***
I should say bug 106889 is exactly the same as this one and yes it is
__builtin_strlen a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119856
Jerry DeLisle changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Depends on|
99 matches
Mail list logo