Re: [swift-dev] Marking a function as __attribute__((weak))

2017-03-06 Thread Philippe Hausler via swift-dev
> On Mar 6, 2017, at 5:59 PM, Greg Parker wrote: > > >> On Mar 6, 2017, at 5:48 PM, Philippe Hausler via swift-dev >> wrote: >> >> Is there a way to mark a function in swift (on Linux) to use the same >> emission strategy as weak declarations in c? >> >> I was to tinkering with some idea

Re: [swift-dev] Marking a function as __attribute__((weak))

2017-03-06 Thread Greg Parker via swift-dev
> On Mar 6, 2017, at 5:48 PM, Philippe Hausler via swift-dev > wrote: > > Is there a way to mark a function in swift (on Linux) to use the same > emission strategy as weak declarations in c? > > I was to tinkering with some ideas on fixing some poor behavior in > swift-corelibs-foundation a

[swift-dev] Marking a function as __attribute__((weak))

2017-03-06 Thread Philippe Hausler via swift-dev
Is there a way to mark a function in swift (on Linux) to use the same emission strategy as weak declarations in c? I was to tinkering with some ideas on fixing some poor behavior in swift-corelibs-foundation and weak would potentially solve this specific case. For reference this is the syntax

Re: [swift-dev] JIT-ting Swift

2017-03-06 Thread Robert Widmann via swift-dev
We used to have a callback in the standard library that would set the process arguments, but that approach was fragile and would still have broken here. Instead, we load the Swift standard library (a step we would have had to do anyway) before entering main and call out to platform-specific fun

Re: [swift-dev] JIT-ting Swift

2017-03-06 Thread Alex Denisov via swift-dev
> The `main` entry point ought to be a standard C "main" function. The argv > argument is an UnsafeMutablePointer?>, which ought > to be ABI-compatible with a char** in C. That was my assumption when I started, thank you for confirmation :) > When JIT'ing Swift, the value of argv doesn't matte

Re: [swift-dev] JIT-ting Swift

2017-03-06 Thread Robert Widmann via swift-dev
%Sp is not an argument, it is the space necessary to hold a reference to the CommandLine enumeration's static argv member. When JIT'ing Swift, the value of argv doesn't matter because we replace the process' arguments dynamically https://github.com/apple/swift/blob/master/lib/Immediate/Immedi

Re: [swift-dev] JIT-ting Swift

2017-03-06 Thread Brian Gesiak via swift-dev
I think this is the best mailing list for your question, but as for a mailing list dedicated to swift-corelibs-xctest: swift-corelibs-...@swift.org is for corelibs-libdispatch, corelibs-foundation, and corelibs-xctest. - Brian Gesiak On Mon, Mar 6, 2017 at 12:33 PM, Alex Denisov via swift-dev <

Re: [swift-dev] JIT-ting Swift

2017-03-06 Thread Joe Groff via swift-dev
> > On Mar 6, 2017, at 9:33 AM, Alex Denisov via swift-dev > wrote: > > Hi there, > > I could not find a list for swift-corelibs-xctest so I am posting it here. > > I am trying to run tests based on XCTest > (https://github.com/apple/swift-corelibs-xctest) using LLVM's JIT. > Everything is w

[swift-dev] JIT-ting Swift

2017-03-06 Thread Alex Denisov via swift-dev
Hi there, I could not find a list for swift-corelibs-xctest so I am posting it here. I am trying to run tests based on XCTest (https://github.com/apple/swift-corelibs-xctest) using LLVM's JIT. Everything is working good so far. However, I am getting a crash. Based on a shallow investigation I ca