https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69246
--- Comment #9 from Richard Henderson <rth at gcc dot gnu.org> ---
There wouldn't be anything wrong with REG_ARGS_SIZE on a
call_pop pattern in and of itself -- in fact I'd expect it.
I don't know if it's worth generating one for a sibcall;
it might be easier to treat it the same as a normal call,
or it might be just as easy to drop the note.
However, there's something whacky about *this* instance.
From the .expand dump,
(call_insn/j 8 7 9 2 (call (mem:QI (reg/f:SI 89) [0 *a.0_2 S1 A8])
(const_int 4 [0x4])) z.c:8 -1
(expr_list:REG_CALL_DECL (nil)
(expr_list:REG_ARGS_SIZE (const_int -4 [0xfffffffffffffffc])
(nil)))
This number is supposed to be the number of bytes accumulated
for a call site. It should *never* be a negative number.
