https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
--- Comment #79 from rguenther at suse dot de <rguenther at suse dot de> --- On Mon, 3 Jan 2022, dcb314 at hotmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860 > > --- Comment #77 from David Binderman <dcb314 at hotmail dot com> --- > (In reply to rguent...@suse.de from comment #76) > > Maybe the issue reproduces with only -mtune=bdver2 or with -march=bdver2 > > -mno-xop (XOP is what's removed from znver2 for example, not 100% sure > > that's all, but ...). It does sound like eventually options-save.c > > is miscompiled somehow ... > > Thanks for the guidance. > > I tried a build with -march=bdver2 -mno-xop and it worked fine. > > So the xop feature is the culprit. OK, so can you - in a -march=bdver2 built tree (that then fails) - produce options-save.ii (preprocessed source) and attach that? Can you try whether you get past the failure point when you add -fno-tree-vectorize to just the options-save.o compilation? Can you provide the -v output of the options-save.o compile so we get the exact cc1plus invocation? I'll then try to figure out what goes wrong by looking at the assembly output.
