[Bug c/98627] GCC emits unaligned memory access instructions causing address error exceptions with the 68000 architecture

2021-01-12 Thread noring at nocrew dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98627 --- Comment #8 from Fredrik Noring --- Thanks, Mikael. Users evidently take whatever m68k-* GCC they have at hand and so 68000-projects therefore must have a special configure test to verify that -march=68000 isn't broken with the user's choice o

[Bug c/98627] GCC emits unaligned memory access instructions causing address error exceptions with the 68000 architecture

2021-01-11 Thread noring at nocrew dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98627 Fredrik Noring changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #6 from Fredrik Norin

[Bug c/98627] GCC emits unaligned memory access instructions causing address error exceptions with the 68000 architecture

2021-01-11 Thread noring at nocrew dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98627 Fredrik Noring changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #4 from Fredrik Norin

[Bug c/98627] GCC emits unaligned memory access instructions causing address error exceptions with the 68000 architecture

2021-01-11 Thread noring at nocrew dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98627 --- Comment #2 from Fredrik Noring --- To obtain the object file I can run the command m68k-unknown-linux-gnu-gcc -O1 -march=68000 -c -o address-error.o address-error.c with a cross-compiler made using the Gentoo package sys-devel/crossdev havi

[Bug c/98627] New: GCC emits unaligned memory access instructions causing address error exceptions with the 68000 architecture

2021-01-11 Thread noring at nocrew dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98627 Bug ID: 98627 Summary: GCC emits unaligned memory access instructions causing address error exceptions with the 68000 architecture Product: gcc Version: 9.3.0 Status: UNC

[Bug middle-end/98502] Optimised memcpy breaks __scalar_storage_order__

2021-01-03 Thread noring at nocrew dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98502 --- Comment #2 from Fredrik Noring --- Thanks, Andrew. I felt certain it's a GCC bug. :) Will the patch be backported to GCC 9.x and 10.x? It'll take a while before 11 is commonly available, I think.

[Bug c/98502] New: Optimised memcpy breaks __scalar_storage_order__

2021-01-02 Thread noring at nocrew dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98502 Bug ID: 98502 Summary: Optimised memcpy breaks __scalar_storage_order__ Product: gcc Version: 9.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: