[Bug target/111010] [13/14 regression] error: unable to find a register to spill compiling GCDAProfiling.c since r13-5092-g4e0b504f26f78f

2023-08-22 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010 --- Comment #13 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #11 from Uroš Bizjak --- > Created attachment 55772 > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55772&action=edit > The correct proposed patch > > Eh, sorry fo

[Bug target/111010] [13/14 regression] error: unable to find a register to spill compiling GCDAProfiling.c since r13-5092-g4e0b504f26f78f

2023-08-22 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010 --- Comment #14 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #12 from Uroš Bizjak --- > gcc-13 version: [...] Same here: successfully regtested on i386-pc-solaris2.11; reduced and full testcase compile without issues. Thanks a lot

[Bug c++/111097] mistifying bug triggered by trivial code change

2023-08-22 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/111074] RISC-V: segmentation fault during RTL pass: vsetvl

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111074 --- Comment #1 from CVS Commits --- The releases/gcc-13 branch has been updated by Li Xu : https://gcc.gnu.org/g:93c4226585cc53fd86dfa3ca2d70d5b417d960b3 commit r13-7738-g93c4226585cc53fd86dfa3ca2d70d5b417d960b3 Author: xuli Date: Tue Aug 2

[Bug c++/111097] mistifying bug triggered by trivial code change

2023-08-22 Thread fabio at cannizzo dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097 --- Comment #3 from Fabio Cannizzo --- Hi Richard Using -fno-strict-aliasing the issue disappear, however I am not sure if that is a real fix, or if it is merely circumstantial. As mentioned, there are many other possible workarounds which als

[Bug c++/111097] mistifying bug triggered by trivial code change

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097 --- Comment #4 from Andrew Pinski --- You can mark XV as may_alias attribute to fix the code too.

[Bug c++/111097] mistifying bug triggered by trivial code change

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097 --- Comment #5 from Andrew Pinski --- > Worth noting, this code works correctly with Visual Studio and with clang. Gcc is known to be take more into account when it comes to aliasing rules of c and c++. That is exactly what you are running into

[Bug target/111010] [13/14 regression] error: unable to find a register to spill compiling GCDAProfiling.c since r13-5092-g4e0b504f26f78f

2023-08-22 Thread ubizjak at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010 --- Comment #15 from Uroš Bizjak --- (In reply to r...@cebitec.uni-bielefeld.de from comment #13) > > --- Comment #11 from Uroš Bizjak --- > > Created attachment 55772 [details] > > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55772&act

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-22 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #6 from Mikael Morin --- (In reply to Mikael Morin from comment #5) > Here sym->formal_ns is NULL because the symbol C has not been completely > setup. This makes the following an "obvious" fix: diff --git a/gcc/fortran/decl.cc b/g

[Bug target/111010] [13/14 regression] error: unable to find a register to spill compiling GCDAProfiling.c since r13-5092-g4e0b504f26f78f

2023-08-22 Thread ro at CeBiTec dot Uni-Bielefeld.DE via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010 --- Comment #16 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #15 from Uroš Bizjak --- > (In reply to r...@cebitec.uni-bielefeld.de from comment #13) >> > --- Comment #11 from Uroš Bizjak --- >> > Created attachment 55772 [details]

[Bug target/111010] [13/14 regression] error: unable to find a register to spill compiling GCDAProfiling.c since r13-5092-g4e0b504f26f78f

2023-08-22 Thread ubizjak at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010 Uroš Bizjak changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at

[Bug fortran/49588] DATA statement with vector sections rejected (ICE: TODO)

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49588 --- Comment #5 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:d3b5a1bccc219680dc19281b6fd6cc798bb679eb commit r14-3380-gd3b5a1bccc219680dc19281b6fd6cc798bb679eb Author: Harald Anlauf Date: Mo

[Bug tree-optimization/111098] New: Missed combine .FMA + .COND_NEG

2023-08-22 Thread lehua.ding at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111098 Bug ID: 111098 Summary: Missed combine .FMA + .COND_NEG Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimizatio

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-22 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #7 from JuzheZhong --- (In reply to Mikael Morin from comment #6) > (In reply to Mikael Morin from comment #5) > > Here sym->formal_ns is NULL because the symbol C has not been completely > > setup. > > This makes the following an "

[Bug analyzer/111099] New: -fanalyzer -Os segmentation fault

2023-08-22 Thread alexey.lapshin at espressif dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111099 Bug ID: 111099 Summary: -fanalyzer -Os segmentation fault Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-22 Thread tkoenig at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 --- Comment #3 from Thomas Koenig --- (In reply to Andrew Pinski from comment #2) > See https://gcc.gnu.org/pipermail/gcc-patches/2016-September/456662.html > > I think this is by design of the ABI ... The workaround mentioned in the thread do

[Bug target/94865] Failure to combine unpckhpd+unpcklpd into blendps

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94865 --- Comment #3 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:27de9aa152141e7f3ee66372647d0f2cd94c4b90 commit r14-3381-g27de9aa152141e7f3ee66372647d0f2cd94c4b90 Author: Richard Biener Date:

[Bug tree-optimization/93080] insert of an extraction on the same location is not optimized

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93080 --- Comment #8 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:27de9aa152141e7f3ee66372647d0f2cd94c4b90 commit r14-3381-g27de9aa152141e7f3ee66372647d0f2cd94c4b90 Author: Richard Biener Date:

[Bug rtl-optimization/94864] Failure to combine vunpckhpd+movsd into single vunpckhpd

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94864 --- Comment #5 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:27de9aa152141e7f3ee66372647d0f2cd94c4b90 commit r14-3381-g27de9aa152141e7f3ee66372647d0f2cd94c4b90 Author: Richard Biener Date:

[Bug target/94865] Failure to combine unpckhpd+unpcklpd into blendps

2023-08-22 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94865 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug rtl-optimization/94864] Failure to combine vunpckhpd+movsd into single vunpckhpd

2023-08-22 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94864 Richard Biener changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug target/94866] Failure to optimize pinsrq of 0 with index 1 into movq

2023-08-22 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94866 Bug 94866 depends on bug 94864, which changed state. Bug 94864 Summary: Failure to combine vunpckhpd+movsd into single vunpckhpd https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94864 What|Removed |Added ---

[Bug tree-optimization/93080] insert of an extraction on the same location is not optimized

2023-08-22 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93080 --- Comment #9 from Richard Biener --- The testcase in the description is fixed, comment#2 and comment#4 are not.

[Bug c++/111097] mistifying bug triggered by trivial code change

2023-08-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097 --- Comment #6 from Jonathan Wakely --- (In reply to Fabio Cannizzo from comment #3) > Using -fno-strict-aliasing the issue disappear, however I am not sure if > that is a real fix, or if it is merely circumstantial. When creating the bug repor

[Bug gcov-profile/111100] New: Use extern "C" for __gcov_dump and related functions in gcov.h

2023-08-22 Thread carlosgalvezp at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=00 Bug ID: 00 Summary: Use extern "C" for __gcov_dump and related functions in gcov.h Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug c++/111097] mistifying bug triggered by trivial code change

2023-08-22 Thread fabio at cannizzo dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111097 --- Comment #7 from Fabio Cannizzo --- Apologies for my ignorance. Thank you.

[Bug sanitizer/111063] [UBSAN] Implement "-inf is outside the range of representable values of type 'unsigned long'" to be on par with Clang

2023-08-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111063 Jonathan Wakely changed: What|Removed |Added Status|RESOLVED|NEW Resolution|INVALID

[Bug sanitizer/111063] [UBSAN] Implement "-inf is outside the range of representable values of type 'unsigned long'" to be on par with Clang

2023-08-22 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111063 --- Comment #4 from Jakub Jelinek --- Yet, even for C++ both the compiler middle-end and users assume they can do say 0.0 / 0.0 and get a NaN, not UB etc. Even for the conversions, the generated code or library functions just set the resulting

[Bug middle-end/111054] [14 Regression] ICE: in to_sreal, at profile-count.cc:472 with -O3 -fno-guess-branch-probability

2023-08-22 Thread hubicka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111054 --- Comment #2 from Jan Hubicka --- This is a missing check for profile presence (we can not convert undefined probability to sreal). I will fix that.

[Bug target/94866] Failure to optimize pinsrq of 0 with index 1 into movq

2023-08-22 Thread ubizjak at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94866 Uroš Bizjak changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at

[Bug gcov-profile/111100] Use extern "C" for __gcov_dump and related functions in gcov.h

2023-08-22 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=00 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug debug/111080] [11/12/13/14 Regression] restrict qualifier causes extra debug info to happen

2023-08-22 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111080 Richard Biener changed: What|Removed |Added Keywords|needs-bisection | Priority|P3

[Bug rtl-optimization/111101] New: -finline-small-functions may invert FP arguments breaking FP bit accuracy in case of NaNs

2023-08-22 Thread pavel.morozkin at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=01 Bug ID: 01 Summary: -finline-small-functions may invert FP arguments breaking FP bit accuracy in case of NaNs Product: gcc Version: 11.3.0 Status: UNCONFIRMED

[Bug rtl-optimization/111101] -finline-small-functions may invert FP arguments breaking FP bit accuracy in case of NaNs

2023-08-22 Thread amonakov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=01 Alexander Monakov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #21 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:145da6a8e1ad60f048069012d81e37f84e1585fd commit r14-3385-g145da6a8e1ad60f048069012d81e37f84e1585fd Author: Jakub Jelinek Date:

[Bug c++/106652] [C++23] P1467 - Extended floating-point types and standard names

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106652 --- Comment #22 from CVS Commits --- The releases/gcc-13 branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:e7a097ea72d3295a1a1680ba05c4fc8242bae7f0 commit r13-7743-ge7a097ea72d3295a1a1680ba05c4fc8242bae7f0 Author: Jakub Jelinek

[Bug rtl-optimization/110093] [12/13/14 Regression][avr] Move frenzy leading to code bloat

2023-08-22 Thread gjl at gcc dot gnu.org via Gcc-bugs
t;GCC: (GNU) 14.0.0 20230822 (experimental)"

[Bug rtl-optimization/110093] [12/13/14 Regression][avr] Move frenzy leading to code bloat

2023-08-22 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110093 Georg-Johann Lay changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug c++/102613] [C++23] P2246R1 - Character encoding of diagnostic text

2023-08-22 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102613 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org,

[Bug c++/102613] [C++23] P2246R1 - Character encoding of diagnostic text

2023-08-22 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102613 --- Comment #2 from Jakub Jelinek --- Looking at what clang++ does, they emit 01.C:1:1: error: static_assert failed "\360\237\230\200" etc. and don't really support -finput-charset=ISO-8859-1 etc. (-finput-charset=utf-8 works).

[Bug target/111096] Frame pointer is not used even when -fomit-frame-pointer is specified

2023-08-22 Thread gccbug at provalid dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111096 gccbug at provalid dot com changed: What|Removed |Added CC||gccbug at provalid dot com

[Bug tree-optimization/95929] Failure to optimize tautological comparisons of comparisons to a single one

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95929 Andrew Pinski changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org

[Bug tree-optimization/95929] Failure to optimize tautological comparisons of comparisons to a single one

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95929 --- Comment #5 from Andrew Pinski --- /* -bool is always bool, likewise for abs and absu. */ (for op (negate abs absu) (simplify (op @0) (if (INTEGER_TYPE_P (type) && TYPE_PRECISION (type) == 1) (non_lvalue @0

[Bug libstdc++/111102] New: illegal pointer arithmetic invoked by std::format("L{:65536}",1)

2023-08-22 Thread gcc at pauldreik dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=02 Bug ID: 02 Summary: illegal pointer arithmetic invoked by std::format("L{:65536}",1) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/111091] Split view with double quoted string

2023-08-22 Thread ppalka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111091 Patrick Palka changed: What|Removed |Added CC||ppalka at gcc dot gnu.org S

[Bug libstdc++/111091] Split view with double quoted string

2023-08-22 Thread deco33000 at yandex dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111091 --- Comment #4 from KL --- I get it. Must be more careful :) Thanks

[Bug fortran/33056] [Meta-bug] Data - statement related bugs

2023-08-22 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33056 Bug 33056 depends on bug 49588, which changed state. Bug 49588 Summary: DATA statement with vector sections rejected (ICE: TODO) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49588 What|Removed |Added ---

[Bug fortran/49588] DATA statement with vector sections rejected (ICE: TODO)

2023-08-22 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49588 anlauf at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |14.0 Resolution|---

[Bug c++/70248] constexpr initialization with unspecified equality expression accepted

2023-08-22 Thread pkeir at outlook dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70248 Paul Keir changed: What|Removed |Added CC||pkeir at outlook dot com --- Comment #10 fro

[Bug c++/109751] [13/14 Regression] boost iterator_interface fails concept check starting in gcc-13

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109751 --- Comment #24 from CVS Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:810bcc00156cefce7ad40fc9d8de6e43c3a04450 commit r14-3389-g810bcc00156cefce7ad40fc9d8de6e43c3a04450 Author: Jason Merrill Date: T

[Bug c++/111103] New: gcc accepts bad type syntax

2023-08-22 Thread andrew.bell.ia at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=03 Bug ID: 03 Summary: gcc accepts bad type syntax Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Ass

[Bug c++/111103] gcc accepts bad type syntax

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=03 --- Comment #1 from Andrew Pinski --- Try with -pedantic-errors. This is an extension iirc.

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-22 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #8 from Mikael Morin --- (In reply to JuzheZhong from comment #7) > Do you have a solution that we can fix RISC-V backend? No, this is not RISC-V specific. > Or you will fix it in Fortran front-end? Yes, the fix will have to be in

[Bug fortran/25095] Disallowed intrinsic in initialization statement

2023-08-22 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25095 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|NEW |WAITING CC|

[Bug libstdc++/111102] illegal pointer arithmetic invoked by std::format("L{:65536}",1)

2023-08-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=02 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug c++/111103] gcc accepts bad type syntax

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=03 --- Comment #2 from Andrew Pinski --- : In function 'long long int f()': :6:13: error: 'long long' specified with typedef-name 'U8' [-Wpedantic] 6 | U8 long long i = 23; | ^~~~

[Bug c++/80516] No error for bad type-specifier-seq in template parameter

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80516 --- Comment #6 from Andrew Pinski --- The error message with -pedantic is now: :7:3: error: 'signed' specified with typedef-name 'using u = unsigned int' [-Wpedantic] 7 | S s; | ^~

[Bug c++/111103] gcc accepts bad type syntax

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=03 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRME

[Bug c++/80516] No error for bad type-specifier-seq in template parameter

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80516 Andrew Pinski changed: What|Removed |Added CC||andrew.bell.ia at gmail dot com --- Comm

[Bug c++/111104] New: Fatal error: can't fill 256 bytes in section .rodata

2023-08-22 Thread adavanian at nvidia dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=04 Bug ID: 04 Summary: Fatal error: can't fill 256 bytes in section .rodata Product: gcc Version: 12.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug target/43744] SH: Error: pcrel too far

2023-08-22 Thread giulio.benetti at benettiengineering dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43744 --- Comment #19 from Giulio Benetti --- This bug still shows up with gcc 12.3.0. Can you please reopen it? Thank you

[Bug target/111104] Fatal error: can't fill 256 bytes in section .rodata

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=04 --- Comment #1 from Andrew Pinski --- I don't think there is anything GCC can do here. You requested a huge array which is zero-filled and GCC is able to compile it to the produce assembly code which is valid.

[Bug target/111104] Fatal error: can't fill 256 bytes in section .rodata

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=04 Andrew Pinski changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED

[Bug c++/111105] New: [12/13/14 regression] __attribute__((malloc)) can no longer name a C++ member function

2023-08-22 Thread thiago at kde dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=05 Bug ID: 05 Summary: [12/13/14 regression] __attribute__((malloc)) can no longer name a C++ member function Product: gcc Version: 14.0 Status: UNCONFIRMED S

[Bug c++/111105] [12/13/14 regression] __attribute__((malloc)) can no longer name a C++ member function

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=05 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRME

[Bug c++/98992] attribute malloc error associating a member deallocator with an allocator

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98992 Andrew Pinski changed: What|Removed |Added CC||thiago at kde dot org --- Comment #2 fro

[Bug c++/111106] New: missing ; causes internal compiler error: in dependent_type_p, at cp/pt.cc:27901

2023-08-22 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=06 Bug ID: 06 Summary: missing ; causes internal compiler error: in dependent_type_p, at cp/pt.cc:27901 Product: gcc Version: unknown Status: UNCONFIRMED Seve

[Bug c++/111106] [11/12/13/14 Regression] missing ; causes internal compiler error: in dependent_type_p, at cp/pt.cc:27901

2023-08-22 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=06 Marek Polacek changed: What|Removed |Added Keywords||ice-on-invalid-code Target Milestone|

[Bug c++/111106] missing ; causes internal compiler error: in dependent_type_p, at cp/pt.cc:27901

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=06 Andrew Pinski changed: What|Removed |Added Keywords||error-recovery, |

[Bug c++/111106] missing ; causes internal compiler error: in dependent_type_p, at cp/pt.cc:27901

2023-08-22 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=06 --- Comment #2 from Marek Polacek --- (In reply to Marek Polacek from comment #1) > With s/consteval/contexpr/ ICEs since GCC 10. constexpr

[Bug c++/111106] [11/12/13/14 Regression] missing ; causes internal compiler error: in dependent_type_p, at cp/pt.cc:27901

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=06 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |11.5 Summary|missing ; cause

[Bug c++/111106] [11/12/13/14 Regression] missing ; causes internal compiler error: in dependent_type_p, at cp/pt.cc:27901

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=06 Andrew Pinski changed: What|Removed |Added Priority|P3 |P5

[Bug target/111107] New: i686-w64-mingw32 does not realign stack when __attribute__((aligned)) or __attribute__((vector_size)) are used

2023-08-22 Thread zfigura at codeweavers dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07 Bug ID: 07 Summary: i686-w64-mingw32 does not realign stack when __attribute__((aligned)) or __attribute__((vector_size)) are used Product: gcc Version: 12.2

[Bug target/111107] i686-w64-mingw32 does not realign stack when __attribute__((aligned)) or __attribute__((vector_size)) are used

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07 --- Comment #1 from Andrew Pinski --- This on purpose, it is only callbacks (from libc) and main that needs the realignment here. There are other bug reports for a similar thing for mingw even.

[Bug c++/111103] gcc accepts bad type syntax

2023-08-22 Thread andrew.bell.ia at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=03 --- Comment #4 from Andrew Bell --- What is the purpose of the extension?

[Bug c++/111103] gcc accepts bad type syntax

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=03 --- Comment #5 from Andrew Pinski --- (In reply to Andrew Bell from comment #4) > What is the purpose of the extension? The extension has been there since the C++ front-end was checked into source control years before 1999. I doubt anyone under

[Bug target/111107] i686-w64-mingw32 does not realign stack when __attribute__((aligned)) or __attribute__((vector_size)) are used

2023-08-22 Thread zfigura at codeweavers dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07 --- Comment #2 from Zebediah Figura --- (In reply to Andrew Pinski from comment #1) > This on purpose, it is only callbacks (from libc) and main that needs the > realignment here. I don't understand what you mean? It's not just libc and main th

[Bug target/111107] i686-w64-mingw32 does not realign stack when __attribute__((aligned)) or __attribute__((vector_size)) are used

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07 --- Comment #3 from Andrew Pinski --- https://inbox.sourceware.org/gcc-patches/5969976.Bvae8NF9fS@polaris/

[Bug target/111107] i686-w64-mingw32 does not realign stack when __attribute__((aligned)) or __attribute__((vector_size)) are used

2023-08-22 Thread zfigura at codeweavers dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07 --- Comment #4 from Zebediah Figura --- (In reply to Andrew Pinski from comment #3) > https://inbox.sourceware.org/gcc-patches/5969976.Bvae8NF9fS@polaris/ Again, I'm not sure what you're trying to communicate here. I'm aware that -mstackrealign

[Bug analyzer/105899] RFE: -fanalyzer could complain about misuses of standard C string APIs

2023-08-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105899 --- Comment #4 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:3242fb533d48abab621618c4f183ca395de3dcd2 commit r14-3391-g3242fb533d48abab621618c4f183ca395de3dcd2 Author: David Malcolm Date: T

[Bug tree-optimization/101590] (len & - N) <= len is not optimized to 1

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101590 --- Comment #4 from Andrew Pinski --- U | N < U -> false U & N <= U -> true U & N > U -> false U | N >= U -> true >I don't see an easy way to combine these two patterns though. I totally missed that the for loop is a pair for. (for cmp (lt

[Bug tree-optimization/101590] (len & - N) <= len is not optimized to 1

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101590 --- Comment #5 from Andrew Pinski --- (In reply to Andrew Pinski from comment #4) > U | N < U -> false > U & N <= U -> true > U & N > U -> false > U | N >= U -> true > > >I don't see an easy way to combine these two patterns though. > I totally

[Bug tree-optimization/94884] Failure to recognize that result of or is always superior to operands

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94884 Andrew Pinski changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org

[Bug target/94866] Failure to optimize pinsrq of 0 with index 1 into movq

2023-08-22 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94866 Hongtao.liu changed: What|Removed |Added CC||crazylht at gmail dot com --- Comment #3 f

[Bug tree-optimization/111108] New: (a|c) == (a|c) should be convert into (a&~c) == (a&~c) IFF ~c simplifies

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=08 Bug ID: 08 Summary: (a|c) == (a|c) should be convert into (a&~c) == (a&~c) IFF ~c simplifies Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: miss

[Bug tree-optimization/101650] (len | N) == len is transformed to len & N != 0

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101650 --- Comment #2 from Andrew Pinski --- So the pattern which we have currently matching (X | Y) == Y does this: /* (X | Y) == Y becomes (X & ~Y) == 0. */ (simplify (cmp:c (bit_ior:c @0 @1) @1) (cmp (bit_and @0 (bit_not! @1)) { build_zero_cs

[Bug tree-optimization/71336] Suboptimal code generated for "(a & 1) ? (CST1 + CST2) : CST1"

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71336 --- Comment #11 from Andrew Pinski --- (In reply to Andrew Pinski from comment #10) > So it should be possible to extend the match pattern for what was the > two_value_replacement replacement to do this too. > The main thing is instead of differe

[Bug tree-optimization/95034] Failure to convert xor pattern (made out of or+and) to xor

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95034 --- Comment #6 from Andrew Pinski --- So after phiopt2 we end up with: ``` _1 = a_3(D) | b_4(D); if (_1 != 0) goto ; [50.00%] else goto ; [50.00%] [local count: 536870912]: _5 = a_3(D) & b_4(D); _7 = ~_5; [local count: 1

[Bug tree-optimization/95408] Failure to optimize bitwise and with negated conditional using the same operand to conditional with decremented operand

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95408 --- Comment #2 from Andrew Pinski --- In forwprop1 we have: _2 = x.0_1 <= 121210; _3 = (int) _2; _4 = _3 * x_5(D); _6 = _4 != 0; since _3 is zero_one_valued we could do instead: ``` (for cmp (ne eq ) bitop (bit_and bit_io

[Bug tree-optimization/95906] Failure to recognize max pattern with mask

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95906 Andrew Pinski changed: What|Removed |Added Depends on||110949 --- Comment #7 from Andrew Pinski

[Bug tree-optimization/95906] Failure to recognize max pattern with mask

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95906 Bug 95906 depends on bug 54525, which changed state. Bug 54525 Summary: Recognize (vec_)cond_expr in mask operation https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54525 What|Removed |Added

[Bug rtl-optimization/54525] Recognize (vec_)cond_expr in mask operation

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54525 Andrew Pinski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/103536] Suboptimal codegen for && and || combination.

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103536 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement Status|NEW

[Bug tree-optimization/103660] Sub-optimal code with relational operators

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103660 Andrew Pinski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug tree-optimization/103660] Sub-optimal code with relational operators

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103660 --- Comment #3 from Andrew Pinski --- (In reply to Andrew Pinski from comment #2) > Actually: > ``` > (for (op plus bit_ior bit_xor) > (simplify > (op (cond @0 @1 integer_zero_p) > (cond @2 @3 integer_zero_p)) > (with { bool wascmp; }

[Bug tree-optimization/103660] Sub-optimal code with relational operators

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103660 --- Comment #4 from Andrew Pinski --- (In reply to Andrew Pinski from comment #3) > Note I think the patterns added in that revision were incorrect: > + (cond (cmp@0 @01 @02) @3 zerop) > + (cond (icmp@4 @01 @02) @5 zerop)) > > allows for @

[Bug tree-optimization/111109] New: [13/14 Regression] wrong code for some fp comparisons (after r13-4620-g4d9db4bdd458)

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=09 Bug ID: 09 Summary: [13/14 Regression] wrong code for some fp comparisons (after r13-4620-g4d9db4bdd458) Product: gcc Version: 14.0 Status: UNCONFIRMED Key

[Bug tree-optimization/111109] [13/14 Regression] wrong code for some fp comparisons (after r13-4620-g4d9db4bdd458)

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=09 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |13.3

[Bug tree-optimization/111109] [13/14 Regression] wrong code for some fp comparisons (after r13-4620-g4d9db4bdd458)

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=09 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug tree-optimization/111110] New: (A CMP B) != 0 and (A CMP B) == true patterns produce an extra (A CMP B) rather than reusing it

2023-08-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10 Bug ID: 10 Summary: (A CMP B) != 0 and (A CMP B) == true patterns produce an extra (A CMP B) rather than reusing it Product: gcc Version: 14.0 Status: UNCONFIRMED

  1   2   >