Re: [swift-dev] Relative Pointers and Windows ARM

> On May 21, 2016, at 1:01 PM, Saleem Abdulrasool via swift-dev > wrote: > On Thu, May 19, 2016 at 12:29 PM, Joe Groff > wrote: > > > On May 19, 2016, at 12:22 PM, Tom Birch > > wrote: > > > > Would it be acceptable to make relative pointers op

Re: [swift-dev] Relative Pointers and Windows ARM

On Thu, May 19, 2016 at 12:29 PM, Joe Groff wrote: > > > On May 19, 2016, at 12:22 PM, Tom Birch wrote: > > > > Would it be acceptable to make relative pointers optional, so we can pay > the extra load-time cost on platforms where it's hard/undesirable to > implement them? > > That's also a reas

Re: [swift-dev] Relative Pointers and Windows ARM

> On May 19, 2016, at 5:39 PM, Saleem Abdulrasool wrote: > On Thu, May 19, 2016 at 9:07 AM, John McCall > wrote: > > On May 18, 2016, at 1:51 PM, Saleem Abdulrasool > > wrote: > > Hi, > > > > It seems that there are assumptions about the a

Re: [swift-dev] Relative Pointers and Windows ARM

On Thu, May 19, 2016 at 9:07 AM, John McCall wrote: > > On May 18, 2016, at 1:51 PM, Saleem Abdulrasool > wrote: > > Hi, > > > > It seems that there are assumptions about the ability to create relative > address across sections which doesn't seem possible on Windows ARM. > > > > Consider the fol

Re: [swift-dev] Relative Pointers and Windows ARM

> On May 19, 2016, at 12:22 PM, Tom Birch wrote: > > Would it be acceptable to make relative pointers optional, so we can pay the > extra load-time cost on platforms where it's hard/undesirable to implement > them? That's also a reasonable answer, since sliding DLLs is already fairly costly.

Re: [swift-dev] Relative Pointers and Windows ARM

Would it be acceptable to make relative pointers optional, so we can pay the extra load-time cost on platforms where it's hard/undesirable to implement them? cheers, Tom On Thu, May 19, 2016 at 9:51 AM Joe Groff via swift-dev wrote: > > > On May 18, 2016, at 6:01 PM, Saleem Abdulrasool > wrote

Re: [swift-dev] Relative Pointers and Windows ARM

> On May 18, 2016, at 6:01 PM, Saleem Abdulrasool wrote: > > On Wednesday, May 18, 2016, Joe Groff wrote: > > > On May 18, 2016, at 1:51 PM, Saleem Abdulrasool via swift-dev > > wrote: > > > > Hi, > > > > It seems that there are assumptions about the ability to create relative > > address a

Re: [swift-dev] Relative Pointers and Windows ARM

> On May 19, 2016, at 9:07 AM, John McCall via swift-dev > wrote: > >> On May 18, 2016, at 1:51 PM, Saleem Abdulrasool >> wrote: >> Hi, >> >> It seems that there are assumptions about the ability to create relative >> address across sections which doesn't seem possible on Windows ARM. >> >

Re: [swift-dev] Relative Pointers and Windows ARM

> On May 18, 2016, at 1:51 PM, Saleem Abdulrasool wrote: > Hi, > > It seems that there are assumptions about the ability to create relative > address across sections which doesn't seem possible on Windows ARM. > > Consider the following swift code: > > final class _ContiguousArrayStorage { } >

Re: [swift-dev] Relative Pointers and Windows ARM

On Wednesday, May 18, 2016, Joe Groff wrote: > > > On May 18, 2016, at 1:51 PM, Saleem Abdulrasool via swift-dev < > swift-dev@swift.org > wrote: > > > > Hi, > > > > It seems that there are assumptions about the ability to create relative > address across sections which doesn't seem possible on W

Re: [swift-dev] Relative Pointers and Windows ARM

> On May 18, 2016, at 1:51 PM, Saleem Abdulrasool via swift-dev > wrote: > > Hi, > > It seems that there are assumptions about the ability to create relative > address across sections which doesn't seem possible on Windows ARM. > > Consider the following swift code: > > final class _Contigu

[swift-dev] Relative Pointers and Windows ARM

Hi, It seems that there are assumptions about the ability to create relative address across sections which doesn't seem possible on Windows ARM. Consider the following swift code: final class _ContiguousArrayStorage { } When compiled for Windows x86 (via swiftc -c -target i686-windows -parse-as