> On Aug 17, 2015, at 8:06 AM, Abhishek Aggarwal wrote:
>
> Hi Greg
>
> Thanks for your reply. My next queries are based on the Bug 24457 that I
> filed 2-3 days ago.
>
> I analyzed and found the reason of this bug for x86_64-Linux platform.
>
> A solution to fix this bug requires change in
Hi Greg
Thanks for your reply. My next queries are based on the Bug 24457 that I
filed 2-3 days ago.
I analyzed and found the reason of this bug for x86_64-Linux platform.
A solution to fix this bug requires change in the definition of macro
FPR_OFFSET (defined in RegisterInfos_x86_64.h) to calc
> On Aug 14, 2015, at 12:25 AM, Abhishek Aggarwal
> wrote:
>
> Hi
>
> As per my understanding (please correct if I am wrong):
>
> 1. There exists a file for each platform (Architecture+OS) that calculates
> the offsets for that platform. e.g. RegisterContextLinux_x86_64.cpp for
> x86_64 arc
Hi
As per my understanding (please correct if I am wrong):
1. There exists a file for each platform (Architecture+OS) that calculates
the offsets for that platform. e.g. RegisterContextLinux_x86_64.cpp for
x86_64 architecture on Linux OS.
2. For each platform, offset values for registers might b
All registers are placed into one large buffer that contains everything. All
offsets should be the global offset in the register context's data. Typically
we should see:
GPR
rax offset 0
rbx offset 8
FPR
mm0 offset 128
mm1 offset 160
...
EXC
fpsr offset 256
...
So
