https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112830
--- Comment #3 from Richard Biener ---
I think the assert can be relaxed to make truncation OK.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108473
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112827
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
--- Comment #5 from Sam James ---
that's in my bisect range, yeah, got a few steps to go..
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112822
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112820
Richard Biener changed:
What|Removed |Added
Keywords||documentation,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112819
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112836
--- Comment #2 from Sam James ---
Thanks for chasing this down. This has been driving me nuts for a while but I
hadn't dug into it yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112841
--- Comment #2 from Andrew Pinski ---
Note clang also gets this "wrong".
You can see that from:
```
const char* const animals[] = {
"aardvark",
"bluejay",
"catte",
};
int main (int argc, char* argv[]) {
const char* animals2_array1[3];
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112814
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112813
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112841
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112841
Bug ID: 112841
Summary: typeof_unqual is not removing qualifiers from array
types
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
liuhongt at gcc dot gnu.org changed:
What|Removed |Added
CC||liuhongt at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101017
liuhongt at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #9 from JuzheZhong ---
=== gfortran: Unexpected fails for rv64gcv lp64d medany ===
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O0 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O1 output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
liuhongt at gcc dot gnu.org changed:
What|Removed |Added
CC||liuhongt at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112822
--- Comment #3 from Peter Bergner ---
Created attachment 56784
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56784=edit
creduce minimized test case
Attached creduce minimized test case. Use -O3 -mcpu=power10 to recreate.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59390
Andrew Pinski changed:
What|Removed |Added
CC||d.g.gorbachev at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56536
Andrew Pinski changed:
What|Removed |Added
Resolution|FIXED |DUPLICATE
--- Comment #3 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56536
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112813
--- Comment #2 from JuzheZhong ---
https://godbolt.org/z/8bovzxYox
Confirm it has been fixed now.
Could you send a patch with test pr112813.c ? To avoid future regression.
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112572
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112829
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #3 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112788
Kewen Lin changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
Gaius Mulley changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
--- Comment #5 from GCC Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:4e5f5a8ae82c5f4f714102d2437175ec366f644c
commit r14-6100-g4e5f5a8ae82c5f4f714102d2437175ec366f644c
Author: Gaius Mulley
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112829
--- Comment #2 from Alexander Zaitsev ---
Am I right that right now in GCC there are no ready-to-use alternatives to "int
__llvm_profile_write_buffer(char *Buffer)" from LLVM and it should be
implemented somehow manually (as you described)?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112829
--- Comment #1 from Andrew Pinski ---
One way is to simple replace all of the functions in gcov-io.c and implement
them, gcov_open, etc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108473
--- Comment #8 from Andrew Pinski ---
gitlab works but savannah URLs still do not. (the URL I tested is in bug 107333
).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108473
Mark Wielaard changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #7 from Mark
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108473
--- Comment #6 from Mark Wielaard ---
Also looking at f944c5b2a894f866fc50e06ba90fb5dbd902ba36 "Bug 1167919: See
Also: support debbugs.gnu.org tracker"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
Thomas Schwinge changed:
What|Removed |Added
CC||tschwinge at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112837
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
Gaius Mulley changed:
What|Removed |Added
CC||gaius at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
--- Comment #2 from Gaius Mulley ---
Following up on commit: 301dec8533460152c4dd61f46c8e9276e169c49a.
Indeed m2 shouldn't attempt to generate target libraries when performing make
all-gcc. Currently it generates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112830
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112837
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101017
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2021-12-19 00:00:00 |2023-12-3
--- Comment #4 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100988
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91354
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89270
Andrew Pinski changed:
What|Removed |Added
CC||saaadhu at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112840
--- Comment #1 from Andrew Pinski ---
This seems more like something for analyzier rather than a generic warning due
to it requires keeping track of the path where the access is located.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112840
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112840
Bug ID: 112840
Summary: feature request: warn on incorrect tagged union value
access
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112831
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112831
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102199
Andrew Pinski changed:
What|Removed |Added
CC||luigighiron at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112839
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112839
Bug ID: 112839
Summary: Unable to default initialize member variable in
specific circumstances
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112838
--- Comment #3 from Andrew Pinski ---
(In reply to Ahmad Nour from comment #2)
>
> Thanks for confirmation.
> I tried with clang-12 -Wall -Wextra main.cpp, but I didn't get that
> hint/note. Am I missing something?
Oh I tried with -std=c++20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112838
--- Comment #2 from Ahmad Nour ---
(In reply to Andrew Pinski from comment #1)
> Confirmed, I thought I had saw an issue filed that is very smilar to this.
>
>
> Note clang provides the context:
>
> :5:7: note: in instantiation of member
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112835
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112838
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-12-03
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112838
Bug ID: 112838
Summary: Compiler is unable to show the exact error location
when calling copy ctor for a non-copyable object
Product: gcc
Version: 10.5.0
Status:
203175403-geef6aea3052-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231203 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112836
--- Comment #1 from Bruno Haible ---
Created attachment 56779
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56779=edit
proposed fix
Although the error is not easily reproducible, it is easy to analyze
and fix:
The piece of error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112836
Bug ID: 112836
Summary: gcc fails when job control is used
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112406
--- Comment #25 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:4c0dc30099d39ef6d1b6c8c81418c726aa660768
commit r14-6096-g4c0dc30099d39ef6d1b6c8c81418c726aa660768
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828
--- Comment #5 from Rich Townsend ---
One more data point: I tried with gfortran 13.2.0 on Linux/Intel and get the
same result as for 13.1.0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96127
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112835
Bug ID: 112835
Summary: inverting the result of memcmp() produces inefficient
code
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112834
Bug ID: 112834
Summary: Class array function selector causes chain of syntax
and other spurious errors
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112831
--- Comment #2 from Florian Weimer ---
Created attachment 56776
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56776=edit
valgrind output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112831
Florian Weimer changed:
What|Removed |Added
CC|fweimer at redhat dot com |fw at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833
--- Comment #1 from Alejandro Colomar ---
Oops, in the reproducer from above, I should only expect a warning at call
site. The definition is correct, since all parameters are restrict, so it's
free to copy one to the other.
Here's a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112807
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112807
--- Comment #3 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:eef6aea3052b4b8a60df211015dafcb4573d19fb
commit r14-6095-geef6aea3052b4b8a60df211015dafcb4573d19fb
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828
--- Comment #4 from Rich Townsend ---
Another data point for MacOS/Intel (10.13.6, High Sierra) -- with the character
vars set to length 64, the crash is as follows:
test(3287,0x7fff8fc11380) malloc: *** error for object 0x7fe44cc03b58:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112833
Bug ID: 112833
Summary: Missing warnings on restrict misuse
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112832
Bug ID: 112832
Summary: [std::format] Broken non-SFINAE-friendly
`set_debug_format()` for `const char *` formatter
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828
--- Comment #3 from Rich Townsend ---
I can get the MWE to barf on MacOS/Arm (Sonoma 14.1.1), gfortran 13.1.0, by
changing the length of the character vars in the main program from 64 to 16.
The error is now:
In file 'test.f90', around line
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828
--- Comment #2 from Rich Townsend ---
The problem manifests with gfortran 13.1.0 on Linux/x86_64. I've run into
similar looking problems on MacOS/Arm, but the MWE I provided seems to work OK
on Arm.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112831
Bug ID: 112831
Summary: ICE: tree check: expected class 'type', have
'exceptional' (error_mark) in
type_has_mode_precision_p, at tree.h:6767
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #3 from Chris Elrod ---
> I thought I hit the important cases, but my non-minimal example still gets
> unnecessary register splits and stack spills, so maybe I missed places, or
> perhaps there's another issue.
Adding the unroll
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828
Francois-Xavier Coudert changed:
What|Removed |Added
CC||fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #2 from Chris Elrod ---
https://godbolt.org/z/3648aMTz8
Perhaps a simpler diff is that you can reproduce by uncommenting the pragma,
but codegen becomes good with it.
template
constexpr auto operator*(OuterDualUA2 a, OuterDualUA2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112788
Thomas Schwinge changed:
What|Removed |Added
Last reconfirmed|2023-12-01 00:00:00 |2023-12-3
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112830
Georg-Johann Lay changed:
What|Removed |Added
Target||avr
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112830
Bug ID: 112830
Summary: internal compiler error: in
convert_memory_address_addr_space_1, at explow.cc:302
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #14 from Jakub Jelinek ---
One thing against adding these builtins (especially when we have a type-generic
builtin which can handle all types, not just some of them) is that clang has
added them completely unorthogonally.
GCC has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89645
Paul Thomas changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112827
--- Comment #2 from Zhendong Su ---
Another test that reproduces at -O1 and above.
[520] % gcctk -O3 small.c
during GIMPLE pass: sccp
small.c: In function ‘main’:
small.c:4:5: internal compiler error: Segmentation fault
4 | int main() {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
--- Comment #7 from Paul Thomas ---
Created attachment 56774
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56774=edit
Features 6.x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
--- Comment #6 from Paul Thomas ---
Created attachment 56773
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56773=edit
Feature 5.12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
--- Comment #5 from Paul Thomas ---
Created attachment 56772
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56772=edit
Features 4.x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
--- Comment #4 from Paul Thomas ---
Created attachment 56771
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56771=edit
Features 2.x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
--- Comment #3 from Paul Thomas ---
Created attachment 56770
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56770=edit
Features 1.x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
Paul Thomas changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112826
--- Comment #4 from Junwei Zeng ---
Thank you for your explanation.
92 matches
Mail list logo
