https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120006
--- Comment #5 from Avraham Hollander <anhollander516 at gmail dot com> --- (In reply to Sam James from comment #4) > I can have a look at reducing if nobody else can, just it may be a few days. > But > are you sure fsck.c is actually the miscompiled file (verified that)? > > > > > I diffed the new preprocessed file with the old one and they were the same, > > so I won't reupload it. > > (It would be -- the object file is what would differ.) I was rushing out the door this morning, but now I'm able to take a closer look at build.log. Here's the command line for creating the fsck binary: /bin/sh ./libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -fsigned-char -fno-common -Wall -Wextra -Waddress-of-packed-member -Wdiscarded-qualifiers -Wformat-security -Wimplicit-function-declaration -Wmissing-declarations -Wmissing-parameter-type -Wmissing-prototypes -Wnested-externs -Wno-missing-field-initializers -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wsign-compare -Wstrict-prototypes -Wtype-limits -Wuninitialized -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-parameter -Wunused-result -Wunused-variable -Wvla -Walloca -Werror=sequence-point -I./libmount/src -I./libblkid/src -O2 -fipa-pta -save-temps -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -o fsck disk-utils/fsck-fsck.o lib/fsck-monotonic.o libmount.la libblkid.la libcommon.la So the fsck binary is made from disk-utils/fsck-fsck.o and lib/fsck-monotonic.o. disk-utils/fsck-fsck.o is compiled from disk-utils/fsck.c: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-apps/util-linux-2.41/work/util-linux-2.41 -include config.h -I/var/tmp/portage/sys-apps/util-linux-2.41/work/util-linux-2.41/include -DLOCALEDIR=\"/usr/share/locale\" -D_PATH_RUNSTATEDIR=\"/run\" -D_PATH_LOCALSTATEDIR=\"/var\" -D_PATH_SYSCONFSTATICDIR=\"/usr/lib\" -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fsigned-char -fno-common -Wall -Wextra -Waddress-of-packed-member -Wdiscarded-qualifiers -Wformat-security -Wimplicit-function-declaration -Wmissing-declarations -Wmissing-parameter-type -Wmissing-prototypes -Wnested-externs -Wno-missing-field-initializers -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wsign-compare -Wstrict-prototypes -Wtype-limits -Wuninitialized -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-parameter -Wunused-result -Wunused-variable -Wvla -Walloca -Werror=sequence-point -I./libmount/src -I./libblkid/src -O2 -fipa-pta -save-temps -c -o disk-utils/fsck-fsck.o `test -f 'disk-utils/fsck.c' || echo '/var/tmp/portage/sys-apps/util-linux-2.41/work/util-linux-2.41/'`disk-utils/fsck.c lib/fsck-monotonic.o is compiled from lib/monotonic.c: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/var/tmp/portage/sys-apps/util-linux-2.41/work/util-linux-2.41 -include config.h -I/var/tmp/portage/sys-apps/util-linux-2.41/work/util-linux-2.41/include -DLOCALEDIR=\"/usr/share/locale\" -D_PATH_RUNSTATEDIR=\"/run\" -D_PATH_LOCALSTATEDIR=\"/var\" -D_PATH_SYSCONFSTATICDIR=\"/usr/lib\" -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fsigned-char -fno-common -Wall -Wextra -Waddress-of-packed-member -Wdiscarded-qualifiers -Wformat-security -Wimplicit-function-declaration -Wmissing-declarations -Wmissing-parameter-type -Wmissing-prototypes -Wnested-externs -Wno-missing-field-initializers -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wsign-compare -Wstrict-prototypes -Wtype-limits -Wuninitialized -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-parameter -Wunused-result -Wunused-variable -Wvla -Walloca -Werror=sequence-point -I./libmount/src -I./libblkid/src -O2 -fipa-pta -save-temps -c -o lib/fsck-monotonic.o `test -f 'lib/monotonic.c' || echo '/var/tmp/portage/sys-apps/util-linux-2.41/work/util-linux-2.41/'`lib/monotonic.c So it could be code from either of those files. How would you narrow that down further?
