[Bug target/91927] New: -mstrict-align doesn't prevent unaligned accesses at -O2 and -O3 on AARCH64 targets

IRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gr.audio at gmail dot com Target Milestone: --- Target: aarch64-elf Hello, I'm writing code for an AARCH64 target, and ran into the follo

[Bug target/91927] -mstrict-align doesn't prevent unaligned accesses at -O2 and -O3 on AARCH64 targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91927 --- Comment #2 from Guillaume --- Thanks for your quick reply. Yes, I actually managed to write a minimal test case showing the problem (attached source file). Compiling it with: aarch64-elf-gcc -mcpu=cortex-a72 -march=armv8-a+crc -O3 -mstrict-a

[Bug target/91927] -mstrict-align doesn't prevent unaligned accesses at -O2 and -O3 on AARCH64 targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91927 --- Comment #4 from Guillaume --- Thanks :) Le sam. 28 sept. 2019 à 02:13, pinskia at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> a écrit : > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91927 > > Andrew Pinski changed: > >What

[Bug target/91927] -mstrict-align doesn't prevent unaligned accesses at -O2 and -O3 on AARCH64 targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91927 --- Comment #5 from Guillaume --- I think I found a work-around for the time being. If you define your packed structs with the 'volatile' qualifier, the bug doesn't seem to show up. May not be completely ideal, but it appears to work, and the re

[Bug libstdc++/80196] fenv_t not declared

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196 Guillaume changed: What|Removed |Added CC||gr.audio at gmail dot com --- Comment #7

[Bug libstdc++/80196] fenv_t not declared

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196 --- Comment #11 from Guillaume --- Thanks! Wasn't happening with previous versions. Is there a workaround?

[Bug libstdc++/80196] fenv_t not declared

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196 --- Comment #14 from Guillaume --- OK, this patch fixes it for me as well.

[Bug c/116211] New: C Functions returning a struct always manipulate the stack pointer on RISC-V targets

Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gr.audio at gmail dot com Target Milestone: --- Here's what I consider a "bug" for RISC-V targets (32 & 64) with GCC 14.1 (tested down to v

[Bug middle-end/116211] C Functions returning a struct always manipulate the stack pointer on RISC-V targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 --- Comment #2 from Guillaume --- Hi, thanks. Yes it looks like it, but I could not reproduce this exact problem with x86_64. Maybe present for other targets though.

[Bug middle-end/116211] C Functions returning a struct always manipulate the stack pointer on RISC-V targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116211 --- Comment #4 from Guillaume --- OK thanks!

[Bug modula2/109675] New: GCC 13.1: the Modula-2 front-end fails to build on some platforms

Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: gr.audio at gmail dot com Target Milestone: --- Happens on any platform on which the 'long unsigned int' type can't hold a pointer (for instance: Windows/mingw64).