Hi William, On Thu, Dec 24, 2015 at 3:15 PM, Dmitri Gribenko via swift-lldb-dev < swift-lldb-...@swift.org> wrote:
> + swift-lldb-dev > > On Thu, Dec 24, 2015 at 3:03 PM, William Dillon via swift-dev > <swift-dev@swift.org> wrote: > > Hi all, > > > > I’m working on addressing issues that are preventing lldb from compiling > on 32-bit arm platforms. Many warnings are generated by the definition of > LLDB_INVALID_ADDRESS as UINT64_MAX. Ultimately, it stems from the fact > that size_t is 32 bits, which changes it to the value to UINT32_MAX > (4294967295). Is it appropriate to define LLDB_INVALID_ADDRESS to be > UINT32_MAX on 32-bit platforms and UINT64_MAX on 64-bit platforms, or > should I change the references to size_t to an explicitly 64-bit type (such > as uint64_t) on all platforms? > LLDB supports 32-bit versions debugging 64-bit hosts and vice versa, so we need LLDB_INVALID_ADDRESS to remain the largest address-sized host we can communicate with. So LLDB_INVALID_ADDRESS needs to remain 64-bit everywhere. It looks like some progress was made on this already as I see we had a swift-lldb pull request on this. Thanks for looking into this! -Todd > > > > Thanks! > > - Will > > _______________________________________________ > > swift-dev mailing list > > swift-dev@swift.org > > https://lists.swift.org/mailman/listinfo/swift-dev > > > > -- > main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if > (j){printf("%d\n",i);}}} /*Dmitri Gribenko <griboz...@gmail.com>*/ > _______________________________________________ > swift-lldb-dev mailing list > swift-lldb-...@swift.org > https://lists.swift.org/mailman/listinfo/swift-lldb-dev > -- -Todd
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
