Re: [swift-dev] [swift-lldb-dev] Proposal for Swift and Ubuntu releases

On Thu, Apr 21, 2016, at 01:12 PM, Todd Fiala via swift-lldb-dev wrote: > Hi all, > I wanted to propose how we can go about handling newer Ubuntu releases > in a systematic way.  This covers how we handle Ubuntu on our CI, but > also reflects where we'll be focusing effort at any given point.  The

Re: [swift-dev] [swift-lldb-dev] Proposal for Swift and Ubuntu releases

Thanks, Ryan. Yes, the intent was to harmonize with the Ubuntu release philosophy. I haven’t heard any opposition to this plan. I’m going to move forward with resourcing and executing on this plan. More communication to follow once those details are worked out. Thanks, all! Sincerely, Todd

Re: [swift-dev] swift (ABI) and Windows

On Tue, Apr 12, 2016 at 9:32 AM, Saleem Abdulrasool wrote: > On Monday, April 11, 2016, Joe Groff wrote: > >> >> > On Apr 11, 2016, at 3:19 PM, Saleem Abdulrasool via swift-dev < >> swift-dev@swift.org> wrote: >> > >> > On Thu, Apr 7, 2016 at 2:12 PM, Saleem Abdulrasool < >> compn...@compnerd.or

Re: [swift-dev] swift (ABI) and Windows

> On Apr 26, 2016, at 8:43 AM, Saleem Abdulrasool wrote: > On Tue, Apr 12, 2016 at 9:32 AM, Saleem Abdulrasool > wrote: > On Monday, April 11, 2016, Joe Groff > wrote: > > > On Apr 11, 2016, at 3:19 PM, Saleem Abdulrasool via swift-dev > >

[swift-dev] hmap files

What are hmap files and how do they relate to the swift compilation process? It seems that they are a clang thing, but I can't find any documentation on them. ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-de

Re: [swift-dev] hmap files

They are "header map" files and you are right they are very poorly documented. Xcode uses them to provide the compiler with a mapping of textual include names to actual file paths. What are you specifically looking into? - Daniel > On Apr 26, 2016, at 11:42 AM, Rafkind, Jon via swift-dev >

Re: [swift-dev] hmap files

Well I'm wondering what to do with them since I am writing a program that directly invokes the swift compiler code. Meaning, I create a swift::Module*, call swift::parseIntoSourceFile, swift::performTypeChecking, etc. So far it doesn't seem that I need to pass along the hmap files to anything in th

Re: [swift-dev] hmap files

Yes, you should avoid passing header map files. They should only be used when trying to integrate with existing Xcode projects, when invoking swiftc yourself you should use the simpler header search path options (-I, -F). - Daniel > On Apr 26, 2016, at 11:51 AM, Rafkind, Jon wrote: > > Well

Re: [swift-dev] [Compiler] Help IR gen in targetting MSVC

The problem can be solved by modifying that code. Thanks you. I thought that code will affect only to the CLong type not Int. But I meet another problem to fix it. I couldn't find the conditional method to distinct x86_64-*-windows-msvc with x86_64-*-windows-cygnus in Swift source. "#if os(Window

Re: [swift-dev] [Compiler] Help IR gen in targetting MSVC

> On Apr 26, 2016, at 1:03 PM, Sangjin Han wrote: > The problem can be solved by modifying that code. Thanks you. I thought that > code will affect only to the CLong type not Int. It changes what 'long' gets imported as. If there's a Windows API defined using 'long' (rather than some more mean

Re: [swift-dev] [swift-evolution] [Compiler] Help IR gen in targetting MSVC

> On Apr 26, 2016, at 1:24 PM, John McCall via swift-evolution > wrote: > >> On Apr 26, 2016, at 1:03 PM, Sangjin Han wrote: >> The problem can be solved by modifying that code. Thanks you. I thought that >> code will affect only to the CLong type not Int. > > It changes what 'long' gets imp

Re: [swift-dev] [swift-evolution] [Compiler] Help IR gen in targetting MSVC

> On Apr 26, 2016, at 1:39 PM, Joe Groff wrote: >> On Apr 26, 2016, at 1:24 PM, John McCall via swift-evolution >> wrote: >> >>> On Apr 26, 2016, at 1:03 PM, Sangjin Han wrote: >>> The problem can be solved by modifying that code. Thanks you. I thought >>> that code will affect only to the CL

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3669

Fix incoming.,.. > On Apr 26, 2016, at 5:28 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3669] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3669/ > > Project: oss-swift-in

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (master) #4544

The fix to this crasher was probably me - I’ll update the test. Thanks! - Joe > On Apr 26, 2016, at 5:47 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#4544] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4544

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (master) #4544

Hmm… My update didn’t do the trick. Taking a look… > On Apr 26, 2016, at 5:51 PM, Joe Pamer via swift-dev > wrote: > > The fix to this crasher was probably me - I’ll update the test. > > Thanks! > - Joe > >> On Apr 26, 2016, at 5:47 PM, no-re...@swift.org >> wrote

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (master) #4544

Ok - 80564dcc1fa9b6 should do it. Thanks! - Joe > On Apr 26, 2016, at 6:58 PM, Joe Pamer wrote: > > Hmm… My update didn’t do the trick. Taking a look… > >> On Apr 26, 2016, at 5:51 PM, Joe Pamer via swift-dev > > wrote: >> >> The fix to this crasher was probably me