I notice, recently, in Nevada builds, on x86, that the standard workaround for ::print cpu_t, namely ::print unix`cpu_t, no longer works to print the final machcpu_t portion of the struct.
Never really been clear on why the workaround worked, so I haven't delved into why it's stopped; could someone familiar with type resolution perhaps give a rough overview of the process? It's awfully nice to see those fields without standing on your head to typecast or calculate addresses.
