https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118318
--- Comment #12 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Sam James from comment #11) > I'm not sure what to do next. I can write up instructions for reproducing it > manually w/ a full Firefox build, but that doesn't help much. > > I know I need to identify some training input but FF is itself huge and > trains itself on many tests. How do I break this down into something > manageable? Or is that the wrong way to do this? Should I instead just try and artificially construct some caller of these functions in tx.i and hope that works out?
