https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105930
--- Comment #5 from Linus Torvalds <torva...@linux-foundation.org> --- (In reply to Linus Torvalds from comment #4) > > I'm not proud of that hacky thing, but since gcc documentation is written > in sanskrit, and mere mortals can't figure it out, it's the best I could do. And bu 'sanskrit' I mean 'texi'. I understand that it's how GNU projects are supposed to work, but markdown (or rst) is just *so* much more legible and you really can read it like text. Anyway, that's my excuse for not knowing how to "just generate cc1" for a saner git bisect run. What I did worked, but was just incredibly ugly. There must be some better way gcc developers have when they want to bisect cc1 behavior.
