https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94895
--- Comment #2 from Arseny Solokha <asolokha at gmx dot com> --- (In reply to Nicholas Krause from comment #1) > Confirmed however seems to be latent as it seems to be hitting: > case GIMPLE_ASM: > gcc_unreachable (); No, it's not latent. The code you quoted is exactly the immediate cause of this ICE. There's an explicitly asserted assumption in rarely used, virtually unmaintained, nine years old TM code that fails under some exotic artificial circumstances no one cares about. Also, to reason about whether the issue was latent or not you really had to bisect it, though this case is trivial and doesn't even need bisection as the issue was in the file from its inception. There's little value in simply pointing out that gcc_unreachable () w/o understanding what exactly went wrong there. Anyone can do that. And anyone can also run git blame on the file in question or click 'blame' in gitweb. If you really want to help out, please come up w/ correct analysis which would result in a good patch fixing the issue. Thanks. > in expand_block_tm and the commit mentioned is touching coroutines. How does the mentioned commit have to do w/ the issue?!
