https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115314
Bug ID: 115314
Summary: Type of the `auto` template parameter in a concept is
not decayed when called as dependent name
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111536
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111536
Andrew Pinski changed:
What|Removed |Added
CC||llvm at rifkin dot dev
--- Comment #1 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313
--- Comment #1 from Jeremy R. ---
Reduced:
#include
std::string foo() {
std::string str;
return str;
}
: In function 'std::string foo()':
:4:17: warning: use of uninitialized value '' [CWE-457]
[-Wanalyzer-use-of-uninitialized-value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313
Bug ID: 115313
Summary: False positive -fanalyzer use of uninitialized value
due to std::string's default constructor
Product: gcc
Version: 14.1.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
--- Comment #8 from Eric Gallager ---
It might also be worth comparing against the attributes [[unsequenced]] and
[[reproducible]] proposed for the C standard:
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2956.htm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100
--- Comment #8 from Kevin Puetz ---
Found it: this is a duplicate of bug 91507, thus fixed by
r276403/31632e2c4327146ea8d21cff33adaa505b17d2bd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100
--- Comment #7 from Kevin Puetz ---
Nope, falsified that guess - I just realized compiler explorer can do
dwarfdump, which makes it easy to bisect among the releases they have (if not
actually commit-by-commit). This shows that 9.5.0 (which has r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100
Kevin Puetz changed:
What|Removed |Added
CC||puetzk at puetzk dot org
--- Comment #6 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115312
Bug ID: 115312
Summary: [14/15 Regression] ICE when including a PCH via
compiler option -include
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115284
--- Comment #12 from Hans-Peter Nilsson ---
(In reply to r...@cebitec.uni-bielefeld.de from comment #11)
> > --- Comment #10 from Hans-Peter Nilsson ---
> >> The failure is even earlier here: in a sparc64-unknown-linux-gnu
> >> bootstrap, buil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114275
Nathaniel Shead changed:
What|Removed |Added
CC||paalon1936 at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 115257, which changed state.
Bug 115257 Summary: Error when compiling a program with module and println and
auto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115257
What|Removed |Adde
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115257
Nathaniel Shead changed:
What|Removed |Added
CC||nshead at gcc dot gnu.org
Res
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114867
Nathaniel Shead changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 114867, which changed state.
Bug 114867 Summary: [modules] name lookup issues when a function overload set
is exported from GMF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114867
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106852
Bug 106852 depends on bug 114867, which changed state.
Bug 114867 Summary: [modules] name lookup issues when a function overload set
is exported from GMF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114867
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114867
--- Comment #3 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:85f15ea65a97686ad39af0c14b7dd9a9372e3a19
commit r15-964-g85f15ea65a97686ad39af0c14b7dd9a9372e3a19
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114999
--- Comment #9 from Andrew Pinski ---
```
float f(float a, float b, float x)
{
x = a - b;
float t = 0;
t = t - x;
return t/x;
}
```
! HONOR_NANS (type) && ! HONOR_INFINITIES (type)
```
int f(int a, int b, int A)
{
A = ~A;
int t =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114999
--- Comment #8 from Andrew Pinski ---
```
int f(int x)
{
x = ~x;
int t = (x >= 0 ? x : 0);
int t1 = (x <= 0 ? -x : 0);
return t + t1;
}
```
abs(~x)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115311
--- Comment #1 from Joseph S. Myers ---
This definitely wouldn't work for glibc; we freely use -fno-builtin- when
e.g. aliasing double and long double functions when the formats are the same,
where GCC gives an error if it has the functions as b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115068
--- Comment #1 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:a2fd0812a54cf51520f15e900df4cfb5874b75ed
commit r15-951-ga2fd0812a54cf51520f15e900df4cfb5874b75ed
Author: Robin Dapp
Date: Mon May
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111567
Bug 111567 depends on bug 108896, which changed state.
Bug 108896 Summary: provide "element_count" attribute to give more context to
__builtin_dynamic_object_size() and -fsanitize=bounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108896
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108896
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114996
Jeffrey A. Law changed:
What|Removed |Added
Priority|P4 |P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114996
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
--- Comment #4 from Jeffrey A. Law ---
Agh. I was looking in the main config directory, not common/config. So it all
makes sense now.
So if we go back to your original analysis, I think we can say things are
behaving correctly and we just nee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115311
Bug ID: 115311
Summary: -fno-builtin-xxx allowing anything for xxx
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115296
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803
--- Comment #14 from Alexandre Oliva ---
Thanks.
The other problem the testcase in this PR evidenced was that simd_math.h and
simd_scalar.h seem to disregard _GLIBCXX_USE_C99_MATH_TR1, and on newlib-using
targets, that don't declare in math.h e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115289
--- Comment #3 from Segher Boessenkool ---
This needs backports all the way back to GCC 10 (well, as far back as we can
go, anyway :-) ).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115289
--- Comment #2 from Segher Boessenkool ---
Note that the testcase isn't valid C (you cannot validly access an array of
char as a long int), but the problem is there anyway. I'll try to write a
better testcase.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115310
--- Comment #3 from Florian Weimer ---
This is just following the previous GCC behavior. For example, with GCC 11:
$ gcc -S -Werror=return-type -std=gnu89 t.c
t.c:1:1: error: return type defaults to ‘int’ [-Werror=return-type]
1 | main () {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115310
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #2 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115310
Richard Biener changed:
What|Removed |Added
CC||fweimer at redhat dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115307
--- Comment #1 from Richard Biener ---
The issue is that we probably fold isinff early. On x86 I see already in
.original:
return !(ABS_EXPR u<= 3.4028234663852885981170418348451692544e+38);
I think your option is to provide optabs for isi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115310
Bug ID: 115310
Summary: Option -Werror=return-type is too aggressive with
-std=gnu89
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
--- Comment #3 from rguenther at suse dot de ---
On Fri, 31 May 2024, law at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
>
> --- Comment #2 from Jeffrey A. Law ---
> What still doesn't make sense is why nds32
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115309
Andrew Pinski changed:
What|Removed |Added
Component|middle-end |ipa
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113281
--- Comment #30 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Sandiford
:
https://gcc.gnu.org/g:2602b71103d5ef2ef86000cac832b31dad3dfe2b
commit r13-8813-g2602b71103d5ef2ef86000cac832b31dad3dfe2b
Author: Richard Sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115192
--- Comment #13 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Sandiford
:
https://gcc.gnu.org/g:0836216693749f3b0b383d015bd36c004754f1da
commit r13-8812-g0836216693749f3b0b383d015bd36c004754f1da
Author: Richard Sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115295
Rainer Orth changed:
What|Removed |Added
CC||ibuclaw at gcc dot gnu.org
St
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115309
Bug ID: 115309
Summary: Simple coroutine based generator is not optimized well
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115297
--- Comment #3 from GCC Commits ---
The releases/gcc-14 branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:ec92744de552303a1424085203e1311bd9146f21
commit r14-10264-gec92744de552303a1424085203e1311bd9146f21
Author: Uros Bizjak
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110572
Jonathan Wakely changed:
What|Removed |Added
CC||martin at martin dot st
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803
--- Comment #13 from Matthias Kretz (Vir) ---
I opened PR115308 for the __clang__ issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110572
--- Comment #10 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #1)
> I would argue that the root cause is that Clang does not conform to the
> platform ABI for mingw-w64, which requires __GXX_TYPEINFO_EQUALITY_INLINE=0
> to b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115308
Matthias Kretz (Vir) changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115308
Bug ID: 115308
Summary: std::experimental::simd is not convertible to
NEON intrinsic type with Clang
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110572
--- Comment #9 from Jonathan Wakely ---
Right, for Clang we need:
--- a/libstdc++-v3/libsupc++/typeinfo
+++ b/libstdc++-v3/libsupc++/typeinfo
@@ -73,7 +73,7 @@ namespace __cxxabiv1
// By default follow the old inline rules to avoid ABI change
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110572
--- Comment #8 from Peter Damianov ---
The suggested fix works for g++, but not clang++.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114531
--- Comment #9 from Rama Malladi ---
I wanted us to review this feature implementation given GCC 15 Stage 1
development has started. Thank you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115307
Georg-Johann Lay changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115297
--- Comment #2 from GCC Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:0ac802064c2a018cf166c37841697e867de65a95
commit r15-943-g0ac802064c2a018cf166c37841697e867de65a95
Author: Uros Bizjak
Date: Fri Ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115307
Bug ID: 115307
Summary: [avr] Don't expand isinf() like a built-in
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
--- Comment #2 from Jeffrey A. Law ---
What still doesn't make sense is why nds32 would be special here. It doesn't
do anything special with flag_delete_null_pointer_checks and I don't think it
uses any of the address space hooks. So why does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115306
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115306
Bug ID: 115306
Summary: (X + 1) > Y ? -X : 1 pattern does not handle X=~X nor
X = -X;
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: missed-optimizat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110572
--- Comment #7 from Jonathan Wakely ---
This is the fix I'm suggesting:
--- a/libstdc++-v3/libsupc++/typeinfo
+++ b/libstdc++-v3/libsupc++/typeinfo
@@ -188,6 +188,9 @@ namespace std
#endif
#if __GXX_TYPEINFO_EQUALITY_INLINE || __cplusplus >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803
--- Comment #12 from Matthias Kretz (Vir) ---
I noticed that weird special case for __clang__ and don't recall why it was
needed. I should dig up the reason or remove it, I guess.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110572
--- Comment #6 from Jonathan Wakely ---
(In reply to Peter Damianov from comment #5)
> #include
> int main() { return typeid(0) == typeid(0); }
>
> The following reproduces for me, although strangely only with -std=c++23 and
> -static-libstdc+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115282
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Priority
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115284
--- Comment #11 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #10 from Hans-Peter Nilsson ---
> (In reply to r...@cebitec.uni-bielefeld.de from comment #9)
>> > --- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE > > Uni-Bielefel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115303
--- Comment #2 from Richard Biener ---
Yeah, if requiring vect_shift works for you that's pre-approved.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115304
Richard Biener changed:
What|Removed |Added
Keywords||testsuite-fail
--- Comment #2 from Ric
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
Richard Biener changed:
What|Removed |Added
Target||i686-darwin9
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115278
Richard Biener changed:
What|Removed |Added
Summary|[13/14/15 Regression] |[13/14 Regression]
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115278
--- Comment #9 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:65dbe0ab7cdaf2aa84b09a74e594f0faacf1945c
commit r15-941-g65dbe0ab7cdaf2aa84b09a74e594f0faacf1945c
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803
--- Comment #11 from Alexandre Oliva ---
it's the first test for __clang__ in __int_for_sizeof(), that ends up returning
char() rather than _Schar().
I guess that places the problem entirely on our need for defining __clang__ :-(
Sorry about t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
--- Comment #8 from Iain Sandoe ---
(In reply to Eric Botcazou from comment #7)
> They might come from https://gcc.gnu.org/cgi-bin/gcc-gitref.cgi?r=r15-615
> and, in particular, the change made to libgnarl/s-osinte__darwin.ads, in
> which case t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803
--- Comment #10 from Alexandre Oliva ---
FWIW, I can trigger the problem on arm-eabi (and presumably also on
aarch64-elf, but I haven't tried that) with -D__clang__.
(our vxworks toolchains have to define that macro, for complicated reasons)
h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
--- Comment #7 from Eric Botcazou ---
They might come from https://gcc.gnu.org/cgi-bin/gcc-gitref.cgi?r=r15-615 and,
in particular, the change made to libgnarl/s-osinte__darwin.ads, in which case
the way out would be to duplicate libgnat/s-osloc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
--- Comment #6 from Iain Sandoe ---
a quick look at current results for other platform versions suggests that:
* x86_64-darwin10 [64b runtimes, but 32b kernel] is also affected but
* from darwin11+ [64 kernel] the main fail is FAIL: cxa4001
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
Eric Botcazou changed:
What|Removed |Added
Version|14.0|15.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115292
Iain Sandoe changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #2 from Iain Sandoe ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
--- Comment #4 from Iain Sandoe ---
Created attachment 58322
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58322&action=edit
between 856 and 889
likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
--- Comment #3 from Iain Sandoe ---
Created attachment 58321
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58321&action=edit
between 792 and 856
likewise
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
--- Comment #2 from Iain Sandoe ---
Created attachment 58320
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58320&action=edit
between 644 and 792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
--- Comment #1 from Iain Sandoe ---
Created attachment 58319
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58319&action=edit
between 386 and 644
the results have been somewhat turbulent - so posting the ranges I have in case
it helps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115305
Bug ID: 115305
Summary: [15 Regression] many (162) acats regressions on
i686-darwin9.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105258
--- Comment #7 from Jonathan Wakely ---
The patch needs a little refactoring to share code with std::stacktrace, but it
will be fixed soon.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115278
--- Comment #8 from avieira at gcc dot gnu.org ---
Thanks! Missed that Andrew.
> It's a low-level worker, it relies on the caller to have performed sanity
> checking on the stmt itself. I'm testing a patch doing that.
OK, no strong opinion her
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115282
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2024-05-31
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803
--- Comment #9 from Matthias Kretz (Vir) ---
(In reply to Alexandre Oliva from comment #7)
> FWIW, since the backport, this test started failing in gcc-13 on arm and
> aarch64 targets. Presumably this affects earlier branches as well.
>
> .../
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115304
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115304
--- Comment #1 from Rainer Orth ---
Created attachment 58317
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58317&action=edit
32-bit sparc-sun-solaris2.11 slp-gap-1.c.179t.vect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115304
Bug ID: 115304
Summary: gcc.dg/vect/slp-gap-1.c FAILs
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115303
--- Comment #1 from Rainer Orth ---
Created attachment 58316
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58316&action=edit
32-bit sparc-sun-solaris2.11 pr112325.c.179t.vect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115303
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115303
Bug ID: 115303
Summary: gcc.dg/vect/pr112325.c FAILs
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115278
--- Comment #7 from Andrew Pinski ---
(In reply to avieira from comment #5)
> > I think we fixed similar bug on the read side.
>
> I don't have the best memory, but the one I can remember is PR 111882, where
> we had the SAVE_EXPR. And the the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115278
--- Comment #6 from Richard Biener ---
(In reply to avieira from comment #5)
> > I think we fixed similar bug on the read side.
>
> I don't have the best memory, but the one I can remember is PR 111882, where
> we had the SAVE_EXPR. And the the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115278
avieira at gcc dot gnu.org changed:
What|Removed |Added
CC||avieira at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115300
--- Comment #3 from Richard Biener ---
Can you try --disable-plugin? It might be the mingw equivalent of exporting
all dynamic symbols from the cc1 binary runs into target limitations? It looks
like the default on *-*-mingw* is disabled though
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115297
--- Comment #1 from Uroš Bizjak ---
Created attachment 58315
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58315&action=edit
Proposed patch
any_divmod instructions are modelled with invalid RTX:
[(set (match_operand:DI 0 "register_ope
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113281
--- Comment #29 from Robin Dapp ---
Just to document again: The test case should not be vectorized and at some
point we will adjust the cost model so it is not going to be. I'd prefer to
base that decision on real uarchs rather than adjust the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115278
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
1 - 100 of 112 matches
Mail list logo
