[Bug ipa/114290] GCC output incorrect output with -O2

2024-03-09 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114290 rvalue changed: What|Removed |Added CC||i at rvalue dot moe --- Comment #1 from

[Bug target/110066] [13 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-09-04 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #26 from rvalue --- (In reply to CVS Commits from comment #22) > The trunk branch has been updated by Andrew Pinski : > > https://gcc.gnu.org/g:bbc1a102735c72e3c5a4dede8ab382813d12b058 > > commit

[Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg

2023-05-31 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #3 from rvalue --- (In reply to Andrew Pinski from comment #1) > This also could be a glibc issue. I tried gcc 12.2.1 and 13.1.1 with exactly the same glibc and binutils environments, the 12.2.1 version works while 13.1.1 doesn't.

[Bug target/110066] New: [RISC-V] Segment fault if compiled with -static -pg

2023-05-31 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 Bug ID: 110066 Summary: [RISC-V] Segment fault if compiled with -static -pg Product: gcc Version: 13.1.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/104338] RISC-V: Subword atomics result in library calls

2023-05-16 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338 --- Comment #19 from rvalue --- (In reply to Aurelien Jarno from comment #18) > I wonder if the following patch should also be backported, as it > doesn't make sense to link with -latomic anymore with inline subword atomic > operations Agreed.

[Bug driver/104707] GCC doesn't give default lib path to the linker when multilib is off

2023-04-03 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104707 rvalue changed: What|Removed |Added CC||i at rvalue dot moe --- Comment #8 from

[Bug target/104853] [RISC-V] -march=rv64g not including extension Zifencei

2022-04-15 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 --- Comment #15 from rvalue --- Hi, Kito: I've tried these patches and found that it doesn't work with isa-spec 20190608/20191213. Release 11.2.0 with following patches applied: 9871d39f752b, f41871dfdbd9, f049717d8d50, 330aff0a9f7b,

[Bug target/104338] RISC-V: Subword atomics result in library calls

2022-04-07 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338 rvalue changed: What|Removed |Added CC||i at rvalue dot moe --- Comment #4 from

[Bug target/104853] [RISC-V] -march=rv64g not including extension Zifencei

2022-03-30 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 --- Comment #9 from rvalue --- Hi Kito: Thank you for your follow-up patch! Confirmed that these patches do work. The test program compiles successfully with no `-misa-spec` flag or `-misa-spec=2.2` flag. But when I set `-misa-spec=20190608`

[Bug target/104853] [RISC-V] -march=rv64g not including extension Zifencei

2022-03-12 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 --- Comment #7 from rvalue --- Well, I've found something that could be problematic here: https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/riscv/arch-canonicalize;h=49a6204b9cb64cb0e375c6003c423bf115a0a8a6;hb=HEAD#l60 It's never updated

[Bug target/104853] [RISC-V] -march=rv64g not including extension Zifencei

2022-03-12 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 --- Comment #6 from rvalue --- I've got some verbose output from gcc, and it seems that a duplicate `-march` is passed to `as` $ gcc -c test.c -march=rv64g --verbose Using built-in specs. COLLECT_GCC=/usr/sbin/gcc Target:

[Bug target/104853] [RISC-V] -march=rv64g not including extension Zifencei

2022-03-12 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 --- Comment #5 from rvalue --- (In reply to Kito Cheng from comment #4) > Thanks your info, that cause by the default ISA spec version bump issue, > binutils 2.38 and GCC 11.* using different default ISA spec cause this > issue, I've push a

[Bug target/104853] [RISC-V] -march=rv64g not including extension Zifencei

2022-03-08 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 --- Comment #3 from rvalue --- (In reply to Kito Cheng from comment #2) > Do you mind give few more version info for binutils and configuration info > for gcc? > > You can obtain those info by following two commands: > $ gcc -v > $ as

[Bug target/104853] [RISC-V] -march=rv64g not including extension Zifencei

2022-03-08 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 --- Comment #1 from rvalue --- It do works with `-march=rv64g_zifencei`, but I don't think it's the right way to work.

[Bug target/104853] New: [RISC-V] -march=rv64g not including extension Zifencei

2022-03-08 Thread i at rvalue dot moe via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853 Bug ID: 104853 Summary: [RISC-V] -march=rv64g not including extension Zifencei Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3