Re: Runtime Loader Exported Symbols Address Size

On 19/6/22 5:21 am, Joel Sherrill wrote: > > > On Fri, Jun 17, 2022 at 8:13 PM Chris Johns > wrote: > > On 18/6/22 10:08 am, Joel Sherrill wrote: > > On Fri, Jun 17, 2022, 2:28 PM Alex White > >

Re: Runtime Loader Exported Symbols Address Size

On Fri, Jun 17, 2022 at 8:13 PM Chris Johns wrote: > On 18/6/22 10:08 am, Joel Sherrill wrote: > > On Fri, Jun 17, 2022, 2:28 PM Alex White > > wrote: > > > > Hi, > > > > While testing libdl on AArch64 QEMU, we found a bug where the > exported > >

Re: Runtime Loader Exported Symbols Address Size

On 18/6/22 10:08 am, Joel Sherrill wrote: > On Fri, Jun 17, 2022, 2:28 PM Alex White > wrote: > > Hi, > > While testing libdl on AArch64 QEMU, we found a bug where the exported > symbol table appears to always use 32-bit values for addresses, but where

Re: Runtime Loader Exported Symbols Address Size

On Fri, Jun 17, 2022, 2:28 PM Alex White wrote: > Hi, > > While testing libdl on AArch64 QEMU, we found a bug where the exported > symbol table appears to always use 32-bit values for addresses, but where > the exported symbols table is read in `rtems_rtl_symbol_global_add`, the > addresses are

Runtime Loader Exported Symbols Address Size

Hi, While testing libdl on AArch64 QEMU, we found a bug where the exported symbol table appears to always use 32-bit values for addresses, but where the exported symbols table is read in `rtems_rtl_symbol_global_add`, the addresses are expected to be of size `sizeof(unsigned long)`. This did