Daniel Collin
Daniel Collin
I'm thinking symbol within paraphrases of register like this (if symbol is present, otherwise nothing like above) `rax 0xfadefade (_foobar)`
@hrydgard Did some tests with dropping commas but it becomes hard to read it then and separate out where a specific value is. I tried something like this instead ![screen...
Thanks. Yeah I think that can work good :) Also thinking of how to deal with 256/512 bit registers Instead of trying to cram everything "under one roof" maybe its...
Yeah but even if you have a wide console and line breaks it becomes hard after a while to know exactly what position you are on. What I'm saying that...
Yeah that is what I'm thinking. I think I will start with that approach at least and see how it turns out. Regardless it seems that very few registers views...
What exactly do you mean by sub registers? do you mean `rax, eax, al, ah` for example?
Yeah that works on x86/x64 but many CPUs doesn't have that concept (also SSE registers doesn't have that as well) Personally for me it would be useful to see in...
More testing ![screen shot 2016-07-28 at 15 07 20](https://cloud.githubusercontent.com/assets/350822/17213657/8943f850-54d5-11e6-8680-6d9fe0499940.png) vs ![screen shot 2016-07-28 at 15 14 23](https://cloud.githubusercontent.com/assets/350822/17213760/03b3d83a-54d6-11e6-9698-5aebc4f23832.png)
The idea with the first one is to reduce space when you unfold to the next level. Might be better to have it that way as one can pick the...
First line should be decided by type of register, I would say integer registers should always be hex and vector/float should always be float but maybe it could be configurable...