https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121689
--- Comment #6 from Christian Ehrhardt <christian.ehrhardt at canonical dot com> --- Hi, Sorry I didn't get your ping about that earlier - thanks Doko for the hint. I thought that is what the .in file is for and tried if that would build in an isolated way. I picked the build command I saw and tested it against that. I've done so in a /tmp directory with nothing but the .i file and removed all the includes from the commandline. The following gives me what might be the same diff (I can't execute to test it in this isolated fashion, but it looks like the diff that the original build had). gcc-15 -m64 -mlittle-endian -fdiagnostics-color=auto -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -fstack-protector-strong -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wformat-security -Wformat-y2k -Wignored-qualifiers -Wimplicit-fallthrough=2 -Winit-self -Wmissing-format-attribute -Wmissing-prototypes -Wnested-externs -Wold-style-declaration -Wold-style-definition -Wredundant-decls -Wshadow=local -Wstrict-prototypes -Wtype-limits -Wundef -Wvla -Wwrite-strings -Wno-missing-include-dirs -Wno-psabi -Wno-shift-negative-value -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -ftrivial-auto-var-init=zero -fzero-call-used-regs=used-gpr -O2 -g -Wno-implicit-fallthrough -Wno-error=address -Wno-error=type-limits -save-temps -fPIE -isystem /usr/include/mit-krb5 -D_REENTRANT -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR=1 -isystem../linux-headers -isystemlinux-headers -DCOMPILING_PER_TARGET '-DCONFIG_TARGET="riscv64-softmmu-config-target.h"' '-DCONFIG_DEVICES="riscv64-softmmu-config-devices.h"' -MD -MQ test-pmu.c.o -MF test-pmu.c.o.d -o test-pmu.c.o.fails -c pmu.c.i gcc-15 -m64 -mlittle-endian -fdiagnostics-color=auto -Wall -Winvalid-pch -Werror -std=gnu11 -O2 -g -fno-gcse -fstack-protector-strong -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wformat-security -Wformat-y2k -Wignored-qualifiers -Wimplicit-fallthrough=2 -Winit-self -Wmissing-format-attribute -Wmissing-prototypes -Wnested-externs -Wold-style-declaration -Wold-style-definition -Wredundant-decls -Wshadow=local -Wstrict-prototypes -Wtype-limits -Wundef -Wvla -Wwrite-strings -Wno-missing-include-dirs -Wno-psabi -Wno-shift-negative-value -pthread -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fno-common -fwrapv -ftrivial-auto-var-init=zero -fzero-call-used-regs=used-gpr -O2 -g -Wno-implicit-fallthrough -Wno-error=address -Wno-error=type-limits -save-temps -fPIE -isystem /usr/include/mit-krb5 -D_REENTRANT -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR=1 -isystem../linux-headers -isystemlinux-headers -DCOMPILING_PER_TARGET '-DCONFIG_TARGET="riscv64-softmmu-config-target.h"' '-DCONFIG_DEVICES="riscv64-softmmu-config-devices.h"' -MD -MQ test-pmu.c.o -MF test-pmu.c.o.d -o test-pmu.c.o.works -c pmu.c.i objdump -dgS test-pmu.c.o.fails > test-pmu.c.o.fails.objdump objdump -dgS test-pmu.c.o.works > test-pmu.c.o.works.objdump I do not think that further stripping the .i file of more content has a benefit here, does it?
