[Bug jit/104072] Register variables in libgccjit

2024-04-24 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104072 --- Comment #3 from Andreas Schwab --- FAIL: test-error-register-variable-size-mismatch.c.exe iteration 1 of 5: verify_code: actual: "invalid register name for 'global_variable'" != expected: "data type of 'global_variable' isn't suitable for a

[Bug target/113790] [14 Regression][riscv64] ICE in curr_insn_transform, at lra-constraints.cc:4294 since r14-4944-gf55cdce3f8dd85

2024-04-16 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113790 Andreas Schwab changed: What|Removed |Added CC||sch...@linux-m68k.org --- Comment #4

[Bug target/114255] [RISC-V] [RVV] unable to find a register to spill

2024-04-16 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114255 Andreas Schwab changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #2 from Andreas

[Bug target/114255] [RISC-V] [RVV] unable to find a register to spill

2024-04-16 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114255 Andreas Schwab changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug target/114639] [riscv] ICE in create_pre_exit, at mode-switching.cc:451

2024-04-16 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114639 Andreas Schwab changed: What|Removed |Added Target Milestone|--- |14.0 Resolution|---

[Bug target/114714] New: [RISC-V][RVV] ICE: insn does not satisfy its constraints (postreload)

2024-04-14 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114714 Bug ID: 114714 Summary: [RISC-V][RVV] ICE: insn does not satisfy its constraints (postreload) Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug libgcc/114689] [14 Regression] libgcc/config/m68k/fpgnulib.c:305: Suspicious coding ?

2024-04-12 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114689 --- Comment #2 from Andreas Schwab --- Nevertheless it's better for clarity to parentize >> inside |.

[Bug target/114673] RISC-V: "L" constraint cannot be used for lui in inline asm

2024-04-10 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114673 --- Comment #1 from Andreas Schwab --- There is a single use in md files: (define_insn "*movcc" [(set (match_operand:GPR 0 "register_operand" "=r,r") (if_then_else:GPR (match_operator 5 "ordered_comparison_operator"

[Bug target/114639] New: [riscv] ICE in create_pre_exit, at mode-switching.cc:451

2024-04-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114639 Bug ID: 114639 Summary: [riscv] ICE in create_pre_exit, at mode-switching.cc:451 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code

[Bug c++/114585] Incorrect boolean value with O2/O3 optimisation

2024-04-04 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114585 Andreas Schwab changed: What|Removed |Added Resolution|--- |INVALID

[Bug go/114454] go.test/test/fixedbugs/issue27836.go FAILs with LANG=C

2024-04-04 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114454 --- Comment #4 from Andreas Schwab --- <83> is the UTF-8 encoding of U00C3 and <84> is the UTF-8 encoding of U0084.

[Bug libquadmath/114533] libquadmath: printf: fix misaligned access on args

2024-04-02 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533 Andreas Schwab changed: What|Removed |Added Status|WAITING |UNCONFIRMED Ever confirmed|1

[Bug libquadmath/114533] libquadmath: printf: fix misaligned access on args

2024-04-02 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug libquadmath/114533] libquadmath: printf: fix misaligned access on args

2024-04-02 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533 --- Comment #3 from Andreas Schwab --- Is the stack properly aligned at this point?

[Bug target/114255] New: [RISC-V] unable to find a register to spill

2024-03-06 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114255 Bug ID: 114255 Summary: [RISC-V] unable to find a register to spill Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal

[Bug target/114168] New: [RISC-V] Compiler generates impossible addend

2024-02-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114168 Bug ID: 114168 Summary: [RISC-V] Compiler generates impossible addend Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/114083] Possible word play on conditional/unconditional

2024-02-24 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083 --- Comment #5 from Andreas Schwab --- Enable conditional-move operations even if unsupported by hardware.

[Bug target/66874] RFE: x86_64_fallback_frame_state more robust

2024-02-23 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66874 --- Comment #5 from Andreas Schwab --- If the unwinder crashes you have either incorrect unwind info or a corrupted stack. Neither should be papered over.

[Bug target/113874] GNU2 TLS descriptor calls do not follow psABI on x86_64-linux-gnu

2024-02-12 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113874 --- Comment #37 from Andreas Schwab --- No, it uses whatever __rtld_malloc points at, which will be the normal malloc after bootstrap.

[Bug target/113874] GNU2 TLS descriptor calls do not follow psABI on x86_64-linux-gnu

2024-02-12 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113874 --- Comment #35 from Andreas Schwab --- ld.so use its internal malloc only during bootstrapping.

[Bug libgcc/113803] libgcc unwinder stops at calls to null function pointer on some targets

2024-02-07 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113803 --- Comment #7 from Andreas Schwab --- Actually, the null return address is coming from the unwind information of __return_rt, which is just a normal function for the unwinder. gdb has special knowlege to detect it as a signal trampoline

[Bug libgcc/113803] libgcc unwinder stops at calls to null function pointer on some targets

2024-02-07 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113803 --- Comment #5 from Andreas Schwab --- The return address is coming from the signal frame, and it is zero here due the null pointer call.

[Bug libgcc/113803] libgcc unwinder stops at calls to null function pointer on some targets

2024-02-07 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113803 --- Comment #3 from Andreas Schwab --- Since DWARF unwinding depends on the unwind info associated with the return address, I don't think anything can be done about that. On powerpc, a backtrace can be constructed from link address that

[Bug libgcc/113803] libgcc unwinder stops at calls to null function pointer on some targets

2024-02-07 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113803 --- Comment #2 from Andreas Schwab --- if (context->ra == 0) return _URC_END_OF_STACK;

[Bug target/111403] LoongArch: Wrong code with -O -mlasx -fopenmp-simd

2024-01-31 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111403 --- Comment #6 from Andreas Schwab --- GDB disables ASLR.

[Bug target/113648] Cross compiler cannot find cross binutils on macOS

2024-01-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113648 --- Comment #4 from Andreas Schwab --- Correction: the preferred location is /Volumes/Toolchain/openwrt/lib/gcc/aarch64-linux-gnu/13.2.0/../../../../aarch64-linux-gnu/bin/ld

[Bug target/113648] Cross compiler cannot find cross binutils on macOS

2024-01-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113648 --- Comment #3 from Andreas Schwab --- The preferred location is /Volumes/Toolchain/openwrt/lib/gcc/aarch64-linux-gnu/13.2.0/../../../../aarch64-linux-gnu/bin/aarch64-linux-gnu/13.2.0/ld (known as gcc_tooldir in the makefile)

[Bug libstdc++/84568] libstdc++-v3 configure checks for atomic operations fail on riscv

2024-01-18 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84568 --- Comment #14 from Andreas Schwab --- Yes, with inline atomics no libatomic is needed any more.

[Bug libstdc++/113230] 27_io/print/1.cc fails when run with qemu

2024-01-04 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113230 --- Comment #4 from Andreas Schwab --- What does "run with qemu" mean exactly?

[Bug target/113045] armv7l-unknown-linux-gnueabihf: valgrind error during build of libcc1

2024-01-02 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113045 --- Comment #23 from Andreas Schwab --- valgrind replaces str/mem functions with its own versions so that it can do better checking and avoid false positives.

[Bug target/109133] Error: operands mismatch -- statement `movec %d0,%cacr' ignored

2024-01-01 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109133 Andreas Schwab changed: What|Removed |Added Resolution|--- |INVALID

[Bug target/113070] [14 regression] [AArch64] [PGO/LTO] Miscompilation of go compiler

2023-12-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113070 Andreas Schwab changed: What|Removed |Added CC||doko at gcc dot gnu.org --- Comment

[Bug go/113173] [14 Regression] libgo fails to build on aarch64-linux-gnu

2023-12-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113173 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/113070] New: [14 regression] [AArch64] [PGO/LTO] Miscompilation of go compiler

2023-12-18 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113070 Bug ID: 113070 Summary: [14 regression] [AArch64] [PGO/LTO] Miscompilation of go compiler Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: lto,

[Bug tree-optimization/113049] Compiles to strlen even with -fno-builtin-strlen -fno-optimize-strlen

2023-12-17 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113049 --- Comment #6 from Andreas Schwab --- That's what -fno-tree-loop-distribute-patterns is for.

[Bug tree-optimization/113049] Compiles to strlen even with -fno-builtin-strlen -fno-optimize-strlen

2023-12-17 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113049 --- Comment #4 from Andreas Schwab --- -fno-builtin-strlen has a different purpose.

[Bug target/113023] RISCV redundant code for loading fixed address

2023-12-14 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113023 --- Comment #5 from Andreas Schwab --- If the linker relaxation does not remove a relaxable move then it is a bug in the linker.

[Bug target/113023] RISCV redundant code for loading fixed address

2023-12-14 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113023 --- Comment #2 from Andreas Schwab --- The insn is _not_ redundant, there is a relocation on it. The linker relaxation will eventually remove it when it becomes unnessessary.

[Bug libquadmath/112963] [14 Regression] Incorrect linking of libquadmath since r14-4863

2023-12-11 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112963 --- Comment #1 from Andreas Schwab --- How did that work before r14-4825-g6a6d3817afa02b?

[Bug target/112918] [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90)

2023-12-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918 --- Comment #7 from Andreas Schwab --- spawn -ignore SIGHUP /daten/aranym/gcc/gcc-20231208/Build/gcc/xgcc -B/daten/aranym/gcc/gcc-20231208/Build/gcc/ /daten/aranym/gcc/gcc-20231208/gcc/testsuite/gcc.dg/torture/vshuf-v16qi.c

[Bug target/112918] [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90)

2023-12-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918 --- Comment #6 from Andreas Schwab --- spawn -ignore SIGHUP /daten/aranym/gcc/gcc-20231208/Build/gcc/xgcc -B/daten/aranym/gcc/gcc-20231208/Build/gcc/ -fdiagnostics-plain-output -mcpu=5235 -Os -c -o pr64461.o

[Bug target/112918] [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90)

2023-12-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918 --- Comment #5 from Andreas Schwab --- spawn -ignore SIGHUP /daten/aranym/gcc/gcc-20231208/Build/gcc/xgcc -B/daten/aranym/gcc/gcc-20231208/Build/gcc/ -fdiagnostics-plain-output -O1 -w -fpermissive -c -o pr82052.o

[Bug target/112918] [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90)

2023-12-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918 --- Comment #4 from Andreas Schwab --- It seems to be related to -fPIC. cc1plus -fpreprocessed floating_from_chars.ii -quiet -mcpu=68020 -O2 -std=gnu++17 -fimplicit-templates -fPIC -o floating_from_chars.s

[Bug target/112918] [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90)

2023-12-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918 --- Comment #3 from Andreas Schwab --- Created attachment 56833 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56833=edit floating_from_chars.ii

[Bug target/112918] New: [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90)

2023-12-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112918 Bug ID: 112918 Summary: [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90) Product: gcc Version: 12.0 Status: UNCONFIRMED

[Bug c/112761] Using incomplete array types in function prototypes doesn't work

2023-11-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112761 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/112543] warning pointer used after free() for printf("%p")

2023-11-15 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112543 --- Comment #1 from Andreas Schwab --- J.2 Undefined behavior (180) The value of a pointer that refers to space deallocated by a call to the free or realloc function is used (7.24.3).

[Bug c/112442] Segfault from casting a ptr when using -O2

2023-11-08 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112442 --- Comment #5 from Andreas Schwab --- warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] 15 | test((char **), "test!");

[Bug target/111600] [14 Regression] RISC-V bootstrap time regression

2023-11-06 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 --- Comment #31 from Andreas Schwab --- For the first time the bootstrap time has been reduced, from 192543 (20231028) to 141231 (20231103), -26,6%.

[Bug middle-end/111921] [11/12/13/14 Regression] ICE with nested function after an error

2023-10-31 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111921 --- Comment #3 from Andreas Schwab --- This is the effect of --enable-checking=release.

[Bug c++/112269] [14 Regression] x86_64 GNU/Linux '-m32' multilib 'libstdc++-v3/include/complex:1493: internal compiler error: in tsubst_expr, at cp/pt.cc:21534'

2023-10-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269 Andreas Schwab changed: What|Removed |Added CC||ppalka at gcc dot gnu.org --- Comment

[Bug c++/112269] [14 Regression] x86_64 GNU/Linux '-m32' multilib 'libstdc++-v3/include/complex:1493: internal compiler error: in tsubst_expr, at cp/pt.cc:21534'

2023-10-29 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269 Andreas Schwab changed: What|Removed |Added Target|x86_64 i?86 |x86_64 i?86 m68k-*-* --- Comment #2

[Bug testsuite/111969] RISC-V rv32gcv: 12 grouped flaky failures

2023-10-25 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111969 --- Comment #2 from Andreas Schwab --- They never fail on real hardware (hifive unleashed).

[Bug preprocessor/111953] stringify operator # rejects "\" but not "\ \" as input

2023-10-24 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111953 --- Comment #1 from Andreas Schwab --- str(\ \ \) is warned again.

[Bug c/111887] GCC: 14: A potential miscompilation with __builtin_inf

2023-10-20 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111887 --- Comment #4 from Andreas Schwab --- Would that break (__FINITE_MATH_ONLY__ ? huge : __builtin_inf())?

[Bug c++/111448] g++ ICE Segmentation fault in qemu-riscv64-static emulator

2023-09-28 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111448 --- Comment #5 from Andreas Schwab --- GCC tries to increase the stack limit to 64Mb, but the qemu user-space emulation uses a fixed stack size (initialized on startup from the current stack limit) and ignores the RLIMIT_STACK request.

[Bug target/111600] [14 Regression] RISC-V bootstrap time regression

2023-09-28 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 --- Comment #9 from Andreas Schwab --- Another problem is that compiling insn-opinit.cc requires insane amount of stack space.

[Bug target/111600] [14 Regression] RISC-V bootstrap time regression

2023-09-27 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 --- Comment #8 from Andreas Schwab --- Native on HiFive Unleashed.

[Bug target/111600] [14 Regression] RISC-V bootstrap time regression

2023-09-27 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 --- Comment #6 from Andreas Schwab --- $ wc -l gcc-*/Build/gcc/insn-opinit.cc 6996 gcc-20230714/Build/gcc/insn-opinit.cc 6591 gcc-20230722/Build/gcc/insn-opinit.cc 6809 gcc-20230728/Build/gcc/insn-opinit.cc 6967

[Bug target/111600] [14 Regression] RISC-V bootstrap time regression

2023-09-27 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 --- Comment #4 from Andreas Schwab --- Created attachment 56000 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56000=edit dwarf2out.ii

[Bug target/111600] [14 Regression] RISC-V bootstrap time regression

2023-09-27 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 --- Comment #3 from Andreas Schwab --- Here are the build times of the stage1 compiler: 2023071421573 2023072219932 -7.6% 2023072821608 +8.4% 2023080421841 +1.0% 2023081125016 +14.5% 20230818

[Bug target/111600] New: [14.0 regression] RISC-V bootstrap time regression

2023-09-26 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600 Bug ID: 111600 Summary: [14.0 regression] RISC-V bootstrap time regression Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/111518] relro protection not working in riscv

2023-09-21 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111518 --- Comment #2 from Andreas Schwab --- That's a linker bug, please report to https://sourceware.org/bugzilla/.

[Bug c++/111448] g++ ICE Segmentation fault in qemu-riscv64-static emulator

2023-09-18 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111448 --- Comment #3 from Andreas Schwab --- Also seen with sonic-pi https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/sonic-pi/standard/riscv64 and psi+

[Bug ipa/111437] Some always inline functions are incorrectly warn of as "might not be inlinable"

2023-09-17 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111437 Andreas Schwab changed: What|Removed |Added Resolution|FIXED |INVALID

[Bug c/111400] Missing return sanitization only works in C++

2023-09-13 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111400 --- Comment #3 from Andreas Schwab --- You already have -W[error=]return-type.

[Bug target/110812] Missing TARGET_OPTION_SAVE/RESTORE on riscv

2023-09-12 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110812 Andreas Schwab changed: What|Removed |Added CC||malat at debian dot org --- Comment

[Bug target/111386] flto=auto => lto1: fatal error: target specific builtin not available

2023-09-12 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111386 Andreas Schwab changed: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #2 from Andreas

[Bug ipa/111283] [14 Regression] gnat profilebootstrap broken on trunk 20230902 on 32bit targets

2023-09-04 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111283 --- Comment #4 from Andreas Schwab --- Doesn't fail here, but it uses release checking: https://build.opensuse.org/package/live_build_log/devel:gcc:next/gcc14/openSUSE_Tumbleweed/i586

[Bug c++/111047] Un-silenceable note for ABI parameters 64-byte alignment

2023-08-17 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111047 --- Comment #1 from Andreas Schwab --- -Wno-abi

[Bug libgcc/110955] SIGSEGV in libgcc_s.so.1`classify_object_over_fdes+0x140 on Solaris SPARC with GCC 13 runtime

2023-08-09 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110955 --- Comment #2 from Andreas Schwab --- Maybe the .eh_frame section is not properly terminated, like PR 110066.

[Bug c++/110920] variably-length array declarations as parameters for C compatibility

2023-08-06 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110920 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/109021] accept size parameter in extern C

2023-08-06 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109021 --- Comment #3 from Andreas Schwab --- *** Bug 110920 has been marked as a duplicate of this bug. ***

[Bug target/110812] New: Missing TARGET_OPTION_SAVE/RESTORE on riscv

2023-07-26 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110812 Bug ID: 110812 Summary: Missing TARGET_OPTION_SAVE/RESTORE on riscv Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

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

2023-07-22 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #19 from Andreas Schwab --- Probably also needed for aarch64.

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

2023-07-22 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #17 from Andreas Schwab --- I don't think you need -fno-omit-frame-pointer.

[Bug c++/110749] wrong show float

2023-07-20 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110749 Andreas Schwab changed: What|Removed |Added Resolution|--- |INVALID

[Bug target/110634] Incorrect RISC-V assembly with -fno-omit-frame-pointer

2023-07-11 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110634 --- Comment #4 from Andreas Schwab --- You need to look at a non-leaf function. For a leaf function there is nothing to unwind from.

[Bug target/110611] X86 is not honouring POINTERS_EXTEND_UNSIGNED in m32 code.

2023-07-10 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110611 --- Comment #3 from Andreas Schwab --- uint64_t is neither Pmode nor word_mode here. POINTERS_EXTEND_UNSIGNED is only relevant if POINTER_SIZE is narrower than Pmode.

[Bug target/106895] powerpc64 unable to specify even/odd register pairs in extended inline asm

2023-07-03 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106895 --- Comment #7 from Andreas Schwab --- You are probably looking for a constraint that mirrors the quad_int_reg_operand predicate.

[Bug c/110427] a

2023-06-27 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110427 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/110402] Bogus -Waddress warning that pointer comparison is always true

2023-06-25 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110402 --- Comment #1 from Andreas Schwab --- The error message does not match anything from the test case.

[Bug go/110297] [13/14 Regression] all libgo tests fail on arm-linux-gnueabi and arm-linxu-gnueabihf

2023-06-19 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297 --- Comment #3 from Andreas Schwab --- The problem is in the magic comment in libgo/go/runtine/mem_gccgo.go: //extern mmap func sysMmap(addr unsafe.Pointer, n uintptr, prot, flags, fd int32, off _libgo_off_t_type) unsafe.Pointer This needs to

[Bug go/110297] [13/14 Regression] all libgo tests fail on arm-linux-gnueabi and arm-linxu-gnueabihf

2023-06-19 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110297 --- Comment #2 from Andreas Schwab --- The go side of the mmap C function is using the wrong type for the offset argument. Dump of assembler code for function runtime.mmap: 0xb692c340 <+0>: push{r4, r5, lr} 0xb692c344 <+4>:

[Bug target/109456] `-ffixed` is ignored for `a` registers on RISC-V.

2023-06-11 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109456 --- Comment #10 from Andreas Schwab --- Or "other ABI-mandated fixed roles". This also includes return value registers.

[Bug target/110188] gcc for RISC-V stack aligned error

2023-06-09 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 --- Comment #3 from Andreas Schwab --- According to riscv.h there is a difference between ABI and calling conventions: /* The smallest supported stack boundary the calling convention supports. */ #define STACK_BOUNDARY \ (riscv_abi ==

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

2023-05-31 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #2 from Andreas Schwab --- I cannot reproduce that with glibc 2.37 and binutils 2.40 on openSUSE. I've also tried with -profile which links against -lc_p, no issue either.

[Bug target/110058] New: confusing error message for %c asm output modifier

2023-05-31 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110058 Bug ID: 110058 Summary: confusing error message for %c asm output modifier Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/110036] [12/13 regression] riscv_asan_shadow_offset mismatch with libsanitizer

2023-05-30 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110036 Andreas Schwab changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug target/110036] New: [12/13/14 regression] riscv_asan_shadow_offset mismatch with libsanitizer

2023-05-30 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110036 Bug ID: 110036 Summary: [12/13/14 regression] riscv_asan_shadow_offset mismatch with libsanitizer Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords:

[Bug target/109927] Bootstrap fails for m68k in stage2 compilation of gimple-match.cc

2023-05-24 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927 --- Comment #17 from Andreas Schwab --- The linker just uses TEXT_START_ADDR=0x8000, but mmap can use any address.

[Bug target/109927] Bootstrap fails for m68k in stage2 compilation of gimple-match.cc

2023-05-23 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927 --- Comment #15 from Andreas Schwab --- TASK_SIZE is 0xF000UL on m68k.

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-23 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 Andreas Schwab changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug c++/109936] error: extended character ≠ is not valid in an identifier

2023-05-22 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109936 --- Comment #10 from Andreas Schwab --- > The standard says "Each preprocessing token that is converted to a token > (5.6) shall have the lexical form of a keyword, an identifier, a literal, or > an operator or punctuator." The argument of the

[Bug sanitizer/109674] [14 Regression] linking with libhwasan is now broken

2023-04-30 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109674 --- Comment #3 from Andreas Schwab --- The __lsan symbols are defined in liblsan, but only as local symbols.

[Bug other/109600] 13.0.1-0.15.fc39: missing #include

2023-04-23 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109600 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/109554] Compiler generates incorrect code when the function declared with returned parameterm but no 'return' in its body

2023-04-19 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109554 Andreas Schwab changed: What|Removed |Added Resolution|WONTFIX |INVALID

[Bug c/109554] Compiler generates incorrect code when the function declared with returned parameterm but no 'return' in its body

2023-04-19 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109554 Andreas Schwab changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/100297] FAIL: gfortran.dg/allocatable_function_1.f90 gfortran.dg/reshape_8.f90

2023-04-16 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100297 --- Comment #3 from Andreas Schwab --- "\.data" is the same as ".data", you want either "\\.data" or {\.data}. But it still doesn't lower the probability to match a filename by much.

[Bug middle-end/109530] Warning "is used uninitialized" raised for an initialized variable.

2023-04-16 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109530 --- Comment #2 from Andreas Schwab --- It also doesn't see that setjmp()==0 means that the block is not reached a second time.

  1   2   3   4   >