[swift-users] libswift frontend ios
Jordan Rose
jordan_rose at apple.com
Mon Mar 14 11:44:49 CDT 2016
The Clang importer is used both for SwiftShims and for code generation; you can't just chop it out. You may be able to get away with explicitly passing an empty SDKPath, though; that keeps it from trying to look up things in /.
Just to be sure, you know you won't be able to execute the LLVM IR you emit, right? iOS doesn't support JIT-compiled code (other than the JavaScript JIT).
Jordan
> On Mar 14, 2016, at 4:45 , Ramakrishna Mallireddy via swift-users <swift-users at swift.org> wrote:
>
> Initially I got missing module "Swift" then I provided the missing module and now I am getting error: missing module "SwiftShims".
>
> I have searched the entire swift build generated lib folder and have not found this module except the shims folder.
>
> How do I locate this module, In OSX also I got the same error flow [by deleting the entire lib/swift folder to generate this error/issue] and when I provided the respective swift module & shims directory under lib/swift/shims I was able to past this error message but the same doesn't helping for iOS.
>
> Thanks
> Ramakrishna
>
> On Sat, Mar 12, 2016 at 6:43 PM, Ramakrishna Mallireddy <ramakrishna.malli at gmail.com <mailto:ramakrishna.malli at gmail.com>> wrote:
> If I remove ClangImporter related code in swift front-end, I am able to start the app. so just want to know what features I miss without ClangImporter. I want to emit LLVM IR assembly for pure swift code. ObjC/C is not something I want to deal with right now.
>
> Inputs on any unexpected things I might face going forward without ClangImporter in this regard will greatly helpful.
>
>
> Thanks
> Ramakrishna
>
>
> On Sat, Mar 12, 2016 at 12:53 AM, Joe Groff <jgroff at apple.com <mailto:jgroff at apple.com>> wrote:
>
>> On Mar 11, 2016, at 11:21 AM, Ramakrishna Mallireddy <ramakrishna.malli at gmail.com <mailto:ramakrishna.malli at gmail.com>> wrote:
>>
>> Hi,
>>
>> I have build clang, llvm , swift for iOS and added these libraries to a sample single-view project and the app crash's before it reach appdelegate.
>>
>> Not able to see what going wrong. could anyone help me to move forward. I don't know where this libLLVMContainer came from.
>>
>
> No idea, sorry. You might have better luck asking the LLVM mailing lists, since the crash here is inside LLVM's pass manager.
>
> -Joe
>> * thread #1: tid = 0x253e8, 0x07a3bddb libsystem_pthread.dylib`_pthread_rwlock_check_init + 11, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x40000000)
>>
>> * frame #0: 0x07a3bddb libsystem_pthread.dylib`_pthread_rwlock_check_init + 11
>>
>> frame #1: 0x07a3baf0 libsystem_pthread.dylib`_pthread_rwlock_lock + 25
>>
>> frame #2: 0x07a40fcc libsystem_pthread.dylib`pthread_rwlock_wrlock$UNIX2003 + 23
>>
>> frame #3: 0x0d57ff13 libLLVMContainer.dylib`llvm::sys::RWMutexImpl::writer_acquire() + 19
>>
>> frame #4: 0x0d4dab12 libLLVMContainer.dylib`llvm::PassRegistry::addRegistrationListener(llvm::PassRegistrationListener*) + 34
>>
>> frame #5: 0x0d4d667e libLLVMContainer.dylib`llvm::PassNameParser::PassNameParser() + 78
>>
>> frame #6: 0x0d4cdad3 libLLVMContainer.dylib`_GLOBAL__sub_I_LegacyPassManager.cpp + 1299
>>
>> frame #7: 0x0187e20f
>>
>> frame #8: 0x0187e368
>>
>> frame #9: 0x01879a01
>>
>> frame #10: 0x01879994
>>
>> frame #11: 0x01879994
>>
>> frame #12: 0x01879994
>>
>> frame #13: 0x01879994
>>
>> frame #14: 0x01879994
>>
>> frame #15: 0x01879994
>>
>> frame #16: 0x01879994
>>
>> frame #17: 0x01879994
>>
>> frame #18: 0x01878d54
>>
>> frame #19: 0x01878de3
>>
>> frame #20: 0x0186ec50
>>
>> frame #21: 0x018722c7
>>
>> frame #22: 0x0186e1f9
>>
>> frame #23: 0x8fe97118 dyld`dyld::useSimulatorDyld(int, macho_header const*, char const*, int, char const**, char const**, char const**, unsigned long*) + 1053
>>
>> frame #24: 0x8fe961f2 dyld`dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 202
>>
>> frame #25: 0x8fe92232 dyld`dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 428
>>
>> frame #26: 0x8fe92047 dyld`_dyld_start + 71
>>
>>
>>
>> Thanks
>>
>> Ramakrishna
>>
>>
>> On Wed, Feb 24, 2016 at 3:16 AM, Ramakrishna Mallireddy <ramakrishna.malli at gmail.com <mailto:ramakrishna.malli at gmail.com>> wrote:
>> Thanks Joe, The build is complete.
>>
>> On Wed, Feb 24, 2016 at 2:33 AM, Joe Groff <jgroff at apple.com <mailto:jgroff at apple.com>> wrote:
>> Sorry, it looks like the magic combination is
>>
>> #if defined(__APPLE__)
>> #include <TargetConditionals.h>
>> #endif
>>
>> #if (TARGET_OS_MAC && !TARGET_OS_IPHONE) || defined(__FreeBSD__)
>> ...do REPL stuff...
>> #endif
>>
>> -Joe
>>
>>> On Feb 23, 2016, at 12:42 PM, Ramakrishna Mallireddy <ramakrishna.malli at gmail.com <mailto:ramakrishna.malli at gmail.com>> wrote:
>>>
>>> __MACOSX__ is not defined, where can I defined this, so that it only effects mac build.
>>>
>>> On Wed, Feb 24, 2016 at 1:57 AM, Joe Groff <jgroff at apple.com <mailto:jgroff at apple.com>> wrote:
>>>
>>> > On Feb 23, 2016, at 12:22 PM, Ramakrishna Mallireddy <ramakrishna.malli at gmail.com <mailto:ramakrishna.malli at gmail.com>> wrote:
>>> >
>>> > I am using the build-script that comes with swift repository. If i remove Immediate dir completely from the build, mac_os build complains[as this will always invoke]. If I redefine the #if then I am getting a dozen errors that are part of histedit.h
>>>
>>> You will need to update the other #if __APPLE__ conditions in the file to match too.
>>>
>>> -Joe
>>>
>>>
>>
>>
>>
>
>
>
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20160314/85f060ef/attachment.html>
More information about the swift-users
mailing list