This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 09/28/2016 10:49 AM, Bernd Schmidt wrote:
On 09/28/2016 06:36 PM, Jeff Law wrote:A "p" prefix for pseudos might still be a good idea, but there's still the issue of a real "p0" register name causing confusion.So how do you think we should deal with distinguishing between the different registers that may appear in a dump file?I think the main problem we were trying to solve is making sure we can make future-proof dumps. So that would argue for allowing h0, v0, p0 syntax in the reader, but not printing them out that way by default.
Correct, I'm mostly concerned with future proofing.I'm certainly OK with a flag to create dumps in a form that's easier to parse, but leaving things as-is by default.
Also, if we don't already, allow hard regs to be specified by name in the reader, and maybe even require it for virtuals.
Works for me. jeff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |