Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

> On Jun 23, 2015, at 4:17 AM, Olivier Martin wrote: > > Actually, we had support for LLVM internally for a while (it is actually not > confidential as I published the code beginning of this year: > https://github.com/ARM-software/edk2/tree/armcc6 >

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

:28 To: edk2-devel@lists.sourceforge.net; Olivier Martin Cc: Cohen, Eugene Subject: Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly On 22 June 2015 at 19:26, Olivier

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

d still prefer to use the existing GCC ld script if possible instead of > rolling our own. Since the existing one does not have the > 64 KB gap between the RX and RW segments, and it probably also dodges the > 'Multiple sections' error. > > So perhaps Olivier can explain wher

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

section to be present after .data if your > script was working as expected. > > -Original Message- > From: Olivier Martin [mailto:olivier.mar...@arm.com] > Sent: 22 June 2015 17:43 > To: Cohen, Eugene; edk2-devel@lists.sourceforge.net > Subject: Re: [edk2] [PATCH] BaseT

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

... -- Ard. > -Original Message- > From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org] > Sent: Tuesday, June 16, 2015 2:51 PM > To: edk2-devel@lists.sourceforge.net; Olivier Martin > Subject: Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the > correlation

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

sage- > From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org] > Sent: Tuesday, June 16, 2015 2:51 PM > To: edk2-devel@lists.sourceforge.net; Olivier Martin > Subject: Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the > correlation .text and .data is consistent between

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

Message- From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org] Sent: Wednesday, June 17, 2015 10:48 PM To: edk2-devel@lists.sourceforge.net Subject: Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugge

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

quot; is already 64K aligned (if I am not mistaken). > This matches your observation, right? > > I assume MAXPAGESIZE is a build time constant for ld, so there is not > a lot of wiggle room here unless we switch to a custom linker script. > > -- > Ard. > > > > >

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

Subject: Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly > On Jun 17, 2015, at 3:01 PM, Cohen, Eugene wrote: > > Thanks for the great feedback -- you made m

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

r observation, right? > > I assume MAXPAGESIZE is a build time constant for ld, so there is not > a lot of wiggle room here unless we switch to a custom linker script. > > -- > Ard. > > > > >> -Original Message- >> From: Ard Biesheuvel [mailto:ard.

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

Biesheuvel [mailto:ard.biesheu...@linaro.org] Sent: Tuesday, June 16, 2015 2:51 PM To: edk2-devel@lists.sourceforge.net; Olivier Martin Subject: Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

hes your observation, right? I assume MAXPAGESIZE is a build time constant for ld, so there is not a lot of wiggle room here unless we switch to a custom linker script. -- Ard. > -----Original Message----- > From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org] > Sent: Tuesday, June 16

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

June 16, 2015 9:21 AM To: edk2-devel@lists.sourceforge.net Subject: Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly On 16 June 2015 at 16:50, Cohen, Eugene wrote: >>

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

bugger is unaware of > the PE-COFF conversion and added executable headers. > OK, that makes sense. > -----Original Message- > From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org] > Sent: Tuesday, June 16, 2015 5:56 AM > To: edk2-devel@lists.sourceforge.net > Subject:

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

seTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly On 4 June 2015 at 21:48, Cohen, Eugene wrote: > Oops, left off the contribution agreement line, trying again > > Dear ArmPkg maintain

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

On 4 June 2015 at 21:48, Cohen, Eugene wrote: > Oops, left off the contribution agreement line, trying again > > Dear ArmPkg maintainers (and later BaseTools maintainer), > > This is a fix for debugger correlation of global variables for AArch64 built > on GCC. > > Before this change looking at g

Re: [edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

Oops, left off the contribution agreement line, trying again Dear ArmPkg maintainers (and later BaseTools maintainer), This is a fix for debugger correlation of global variables for AArch64 built on GCC. Before this change looking at global variables with a debugger showed bogus memory locatio

[edk2] [PATCH] BaseTools for AArch64 GCC: Ensure that the correlation .text and .data is consistent between ELF and PE-COFF so the debugger sees global variables correctly

Dear ArmPkg maintainers (and later BaseTools maintainer), This is a fix for debugger correlation of global variables for AArch64 built on GCC. Before this change looking at global variables with a debugger showed bogus memory locations. This is because the offset of the .data section in the ELF