On Thu, Feb 10, 2005 at 10:21:19PM -0500, Ian Lance Taylor wrote:
> I found other cases where an empty vector produces a NULL pointer and
> leads to a later crash. So I don't think it is safe to have an empty
> vector in RTL for the 'E' format.
This surprises me not at all. FYI, typically we put
Ian Lance Taylor writes:
> This patch fixes the immediate crash, but is this the right thing to
> do? Or should I always put something inside the vector, even if there
> is nothing meaningful to put in there?
I found other cases where an empty vector produces a NULL pointer and
leads to a later
I just happened to write
(define_insn "foo"
[(set (match_operand:SI 0 "register_operand" "=r")
(unspec:SI [] 42))]
""
"xxx\t%0")
This is because I have an instruction which sets a register but
doesn't depend on anything visible to gcc. When I tried to rebuild
gcc, genflags crashed,
