https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69195
--- Comment #18 from Zdenek Sojka <zsojka at seznam dot cz> --- (In reply to Bernd Schmidt from comment #17) > Is this reproducible on trunk? What are the exact flags required to pass to > cc1? I'm not getting a difference in REG_EQUIV notes between -fdce and > -fno-dce. Yes, it still fails in trunk (r234047). cc1 commandline is: /repo/gcc-trunk/binary-trunk-234047-checking-yes-rtl-df-nographite-powerpc64/libexec/gcc/powerpc64-unknown-linux-gnu/6.0.0/cc1 -quiet -iprefix /repo/gcc-trunk/binary-trunk-234047-checking-yes-rtl-df-nographite-powerpc64/bin/../lib/gcc/powerpc64-unknown-linux-gnu/6.0.0/ -D__unix__ -D__gnu_linux__ -D__linux__ -Dunix -D__unix -Dlinux -D__linux -Asystem=linux -Asystem=unix -Asystem=posix testcase.c -quiet -dumpbase testcase.c -auxbase testcase -O3 -fno-dce -fno-forward-propagate -o /tmp/ccnx8kGq.s