[Bug c/52381] asm goto output operands diagnostics

marc.glisse at normalesup dot org gcc-bugzilla@gcc.gnu.org
Mon Feb 27 21:13:00 GMT 2012


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52381

--- Comment #2 from Marc Glisse <marc.glisse at normalesup dot org> 2012-02-27 21:08:44 UTC ---
(In reply to comment #1)
> I don't think asm goto was designed to contain more than a computed jump
> instruction.  And I don't know how reliably we could allocate registers
> for outputs on the multiple outgoing edges.
> 
> So, it's definitely by design.

Note that if output was only reliable on the fall-through path, it would
already be useful. It may not have to be all-edges-or-nothing (or it may have
to, I don't know enough). Although that could be confusing...

> Confirmed for the diagnostic issue.

Thanks. While I am asking, I guess that since asm goto involves control flow it
never gets reordered (as opposed to regular asm), but if someone feels like
adding a sentence with this guarantee to the doc it would be helpful too.



More information about the Gcc-bugs mailing list