On Sat, Sep 12, 2020 at 10:37 AM Florian Weimer <f...@deneb.enyo.de> wrote: > > * H. J. Lu via Gcc-patches: > > > + inform (input_location, "the value of the stack pointer after" > > + " an %<asm%> statement must be the same as it was" > > + " before the statement"); > > Would it make sense to generate a stronger worded warning when > generating asynchronous unwind tables? If an asm statement changes > the stackpointer even temporarily, the unwind information won't be > correct.
Is this the right place for such warning? asm statement may touch stack pointer without clobbering it. -- H.J.
