On Sun, 2016-10-02 at 07:04 -0500, Segher Boessenkool wrote: > On Thu, Sep 29, 2016 at 11:36:29AM -0600, Jeff Law wrote: > > On 09/29/2016 11:25 AM, Bernd Schmidt wrote: > > > On 09/29/2016 07:47 PM, David Malcolm wrote: > > > > This patch adds a new function, print_rtx_function, intended > > > > for use > > > > for generating function dumps suitable for parsing by the RTL > > > > frontend, > > > > but also intended to be human-readable, and human-authorable. > > > > > > > (note 1 0 4 (nil) NOTE_INSN_DELETED) > > > > (note 4 1 2 2 [bb 2] NOTE_INSN_BASIC_BLOCK) > > > > (insn 2 4 3 2 (set (mem/c:SI (plus:DI (reg/f:DI 82 > > > > virtual-stack-vars) > > > > (const_int -4 [0xfffffffffffffffc])) [1 > > > > i+0 > > > > S4 A32]) > > > > (reg:SI 5 di [ i ])) t.c:2 -1 > > > > (nil)) > > > > > > I think it might be a good idea to get rid of redundant > > > information like > > > insn numbers for such a dump format. But that can be left for > > > followup > > > patches. > > I would make the same suggestion. The insn # and backend pattern > > name > > (if any) should be omitted in machine-readable dump format. I'm > > fine > > with that as a follow-up as well. > > You need the insn id for (at least) code_label.
I think that Bernd is referring to the INSN_CODE, rather than than INSN_UID.
