https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78694

--- Comment #4 from Sebastian Huber <sebastian.hu...@embedded-brains.de> ---
(In reply to ktkachov from comment #3)
> I can't reproduce on an arm-none-eabi compiler built with RTL checking. Do
> you pass any particular --with-arch/cpu/fpu/float options?

I built an arm-eabi-gcc using GCC version
1e15f9a7488be0a7446c364b93430d20621af476.

I get:

arm-eabi-gcc -mthumb -ftls-model=local-exec -O2 -S task.i
/home/EB/sebastian_h/archive/gcc-git/libgomp/task.c: In function
‘gomp_create_target_task’:
/home/EB/sebastian_h/archive/gcc-git/libgomp/task.c:778:1: error: invalid rtl
sharing found in the insn
 }
 ^
(insn 1584 1583 1585 (unspec_volatile [
            (const:SI (unspec:SI [
                        (symbol_ref:SI ("gomp_tls_data") [flags 0xea] <var_decl
0x7f5f6bc133f0 gomp_tls_data>)
                        (const_int 4 [0x4])
                    ] UNSPEC_TLS))
        ] VUNSPEC_POOL_4) -1
     (nil))
/home/EB/sebastian_h/archive/gcc-git/libgomp/task.c:778:1: error: shared rtx
(const:SI (unspec:SI [
            (symbol_ref:SI ("gomp_tls_data") [flags 0xea] <var_decl
0x7f5f6bc133f0 gomp_tls_data>)
            (const_int 4 [0x4])
        ] UNSPEC_TLS))
/home/EB/sebastian_h/archive/gcc-git/libgomp/task.c:778:1: internal compiler
error: internal consistency failure
0x80f8dd verify_rtx_sharing
        /home/EB/sebastian_h/archive/gcc-git/gcc/emit-rtl.c:2751
0x80f86a verify_rtx_sharing
        /home/EB/sebastian_h/archive/gcc-git/gcc/emit-rtl.c:2784
0x80fc3b verify_insn_sharing
        /home/EB/sebastian_h/archive/gcc-git/gcc/emit-rtl.c:2837
0x814317 verify_rtl_sharing()
        /home/EB/sebastian_h/archive/gcc-git/gcc/emit-rtl.c:2860
0xaa2deb execute_function_todo
        /home/EB/sebastian_h/archive/gcc-git/gcc/passes.c:1982
0xaa37e5 execute_todo
        /home/EB/sebastian_h/archive/gcc-git/gcc/passes.c:2015
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Reply via email to