https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68820
--- Comment #9 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Jan Hubicka from comment #8) > this does not reproduce for me at PPC nor x86-64. Are there any compilation > farm machines that reproduce it? -fno-use-linker-plugin is needed. Following will trigger the abort on Fedora 23 (otherwise OK with the plugin): $ /ssd/uros/gcc-build/gcc/xgcc -B /ssd/uros/gcc-build/gcc -O2 -g -flto -fno-use-linker-plugin -c memops-asm.c $ /ssd/uros/gcc-build/gcc/xgcc -B /ssd/uros/gcc-build/gcc -O2 -g -flto -fno-use-linker-plugin -c main.c $ /ssd/uros/gcc-build/gcc/xgcc -B /ssd/uros/gcc-build/gcc -O2 -g -flto -fno-use-linker-plugin -c memops-asm-lib.c $ /ssd/uros/gcc-build/gcc/xgcc -B /ssd/uros/gcc-build/gcc -O2 -g -flto -fno-use-linker-plugin main.o memops-asm-lib.o memops-asm.o [uros@localhost mem]$ ./a.out Aborted (core dumped) (gdb) r Starting program: /home/uros/test/mem/a.out Program received signal SIGABRT, Aborted. 0x00007ffff7a4fa98 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff7a4fa98 in raise () from /lib64/libc.so.6 #1 0x00007ffff7a5169a in abort () from /lib64/libc.so.6 #2 0x0000000000400967 in memcpy (d=d@entry=0x601120 <y>, s=s@entry=0x601080 <x>, n=<optimized out>) at memops-asm-lib.c:67 #3 0x0000000000400773 in main_test () at memops-asm.c:37 #4 0x00000000004004d3 in main () at main.c:10 The problem is in the call to memcpy, my_memcpy should be called instead.
