Open josharian opened 10 years ago
Urk. Actually, it looks like this is done intentionally in memname (8g/gsubr.c): namebuf[0] = '.'; // keep optimizer from registerizing The question is now: Is this safe, given the downstream users of this information? I see at least two non-optimizer clients of the "autotmp" name -- racewalk and dwarf generation.
racewalk and dwarf both seem to be working okay. I would like to change these names, though. In particular I'd like to use the shorter construct '%c.%d' where the first character can vary according to the kind of name. t.%d for most temps, m.%d for these memory temps in 8g, maybe p.%d for the parameter shadow variables, maybe something different for order.c-introduced temps vs others (because the former are cleaned up better). But that can't happen until 1.4.
Labels changed: added release-go1.4, removed release-go1.3maybe.
Status changed to Accepted.
We can rethink what's left of this once Keith is done with SSA.