On 14.07.2020 10:06, Jan Beulich wrote:
> gcc re-orders top level blocks by default when optimizing. This
> re-ordering results in all our .type directives to get emitted to the
> assembly file first, followed by gcc's. The assembler warns about
> attempts to change the type of a symbol when it was already set (and
> when there's no intervening setting to "notype").
>
> Signed-off-by: Jan Beulich <jbeul...@suse.com>
> ---
> v2: Refine description to no longer claim a gcc change to be the reason.
>
> --- a/tools/tests/x86_emulator/Makefile
> +++ b/tools/tests/x86_emulator/Makefile
> @@ -295,4 +295,9 @@ x86-emulate.o cpuid.o test_x86_emulator.
> x86-emulate.o: x86_emulate/x86_emulate.c
> x86-emulate.o: HOSTCFLAGS += -D__XEN_TOOLS__
>
> +# In order for our custom .type assembler directives to reliably land after
> +# gcc's, we need to keep it from re-ordering top-level constructs.
> +$(call cc-option-add,HOSTCFLAGS-toplevel,HOSTCC,-fno-toplevel-reorder)
> +test_x86_emulator.o: HOSTCFLAGS += $(HOSTCFLAGS-toplevel)
> +
> test_x86_emulator.o: $(addsuffix .h,$(TESTCASES)) $(addsuffix
> -opmask.h,$(OPMASK))
>
