[Bug target/112413] Wrong switch jump table offset

2023-11-12 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413 --- Comment #6 from Vincent Riviere --- (In reply to Mikael Pettersson from comment #4) > Does the `.balignw` filler disappear if you drop `-malign-int`? No, it stays, but its value becomes 2, so it doesn't cause trouble.

[Bug target/112413] Wrong switch jump table offset

2023-11-06 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413 --- Comment #3 from Vincent Riviere --- (In reply to Andrew Pinski from comment #1) > I don't see any issues with the output of gcc. Are you sure this is not a > binutils gnu as issue where the offsets are done incorrectly there. Yes, I'm sure

[Bug target/112413] Wrong switch jump table offset

2023-11-06 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413 --- Comment #2 from Vincent Riviere --- Cause is in gcc/config/m68k/linux.h, macro ASM_RETURN_CASE_JUMP: https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/m68k/linux.h;h=2e1cb5498b86f053d1e9b7c530648dfa186ca4c4;hb=HEAD#l96 jmp %%pc@(2,%0:

[Bug c/112413] New: Wrong switch jump table offset

2023-11-06 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112413 Bug ID: 112413 Summary: Wrong switch jump table offset Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Ass

[Bug c++/111279] New: ICE: Segmentation fault with m68k,SJLJ and -malign-int

2023-09-03 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111279 Bug ID: 111279 Summary: ICE: Segmentation fault with m68k,SJLJ and -malign-int Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug target/88160] Error: register save offset not a multiple of 4 only with optimize

2023-07-26 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88160 --- Comment #4 from Vincent Riviere --- Created attachment 55647 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55647&action=edit Workaround for compiling libgcc with -mcpu=5475 -mshort Here is a patch for GCC 13.1.0. It allows libgcc to b

[Bug target/88160] Error: register save offset not a multiple of 4 only with optimize

2023-07-26 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88160 --- Comment #3 from Vincent Riviere --- There are 2 lightweight workarounds for the OP testcase: -fno-combine-stack-adjustments -fno-omit-frame-pointer $ m68k-elf-gcc -mshort -mcpu=5475 -g -O2 -c test.c /tmp/ccW6hc6h.s: Assembler messages: /tmp/

[Bug target/88160] Error: register save offset not a multiple of 4 only with optimize

2023-07-25 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88160 Vincent Riviere changed: What|Removed |Added CC||vincent.riviere at freesbee dot fr --

[Bug c/110567] New: GCC fails using a register to initialize multiple variables with a constant

2023-07-05 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110567 Bug ID: 110567 Summary: GCC fails using a register to initialize multiple variables with a constant Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity:

[Bug tree-optimization/102725] -fno-builtin leads to call of strlen since r12-4283-g6f966f06146be768

2023-06-02 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102725 --- Comment #8 from Vincent Riviere --- This still happens with m68k-elf-gcc 13.1.0.

[Bug c/106349] New: strlen reimplementation produces infinite loop with -Os

2022-07-18 Thread vincent.riviere at freesbee dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106349 Bug ID: 106349 Summary: strlen reimplementation produces infinite loop with -Os Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Pri