https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68099
--- Comment #8 from Jonathan Ben-Avraham <yba at tkos dot co.il> --- (In reply to Richard Earnshaw from comment #1) > The gcc developers do not use crosstool, so providing us with a config for > it is of no help. Furthermore, un-preprocessed source means we are unlikely > to be able to reproduce the exact conditions leading up to the failure you > see. > > What we do need are: > > 1) The output of "gcc -v", showing how the compiler was actually configured. > 2) *Pre-processed* source that we can feed into our own builds of the > compiler to try to reproduce the problem See attached test.i preprocesor output
