https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70120
mdaniels at qnx dot com <mdaniels at qnx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mdaniels at qnx dot com
--- Comment #15 from mdaniels at qnx dot com <mdaniels at qnx dot com> ---
Created attachment 40828
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40828&action=edit
An additional testcase for 5.4.0
I have seen a similar problem on 5.4. I applied this fix, just without the
aarch64_can_use_per_function_literal_pools_p() check, and it seems to do the
trick.
Attached is a test case that can reproduce with 5.4, but it not very good as it
is fragile to optimization changes. For example, git bisect landed me on
42b45e8 as a fix and not this change.
$ aarch64-unknown-linux-gnueabi-g++ -g -O2 -fPIE -fstack-protector-strong -c -o
/tmp/test.o /tmp/test.ii
/tmp/ccWVZeQe.s: Assembler messages:
/tmp/ccWVZeQe.s: Error: unaligned opcodes detected in executable segment
