emcpy which I knew was the right way to do
it. I'll push the changes to the OSS community then.
Roger R. Cruz
On Dec 26, 2012, at 8:00 AM, Andrew Haley wrote:
> On 12/24/2012 07:53 PM, Roger Cruz wrote:
>>
>>
>> I am compiling this piece of code from an open so
I am compiling this piece of code from an open source project that I wish not
to have to change. The problem is that when compiled for ARM, it generates an
LDRD instruction, which when executed, causes a bus error since the address in
ptr is not doubleword aligned. I know I can change the co
Roger
From: Michael Eager
To: Roger Cruz
Cc: "gcc@gcc.gnu.org" ; "dwarf-disc...@lists.dwarfstd.org"
Sent: Wednesday, June 6, 2012 1:27 PM
Subject: Re: Fw: Extending calling convention information in DWARF output for
x86
On 06/06/2012 09:28 AM, Roger Cruz wrote:
offset: 0x117d6): name
<267c9> DW_AT_decl_file : 2
<267ca> DW_AT_decl_line : 216
<267cb> DW_AT_type : <0x1a509>
<267cf> DW_AT_location : 2 byte block: 91 74 (DW_OP_fbreg: -12)
How can the above information be u
I am interested in parsing DWARF debug output in order to know the calling
convention of each function. Reading the spec for DWARF-4, I can see that
there is an attribute DW_AT_calling_convention but its only defined values are
(pg 52):
DW_CC_normal
DW_CC_program
DW_CC_nocall
The spec als
