Re: [swift-dev] Differences between Xcode official toolchains and tagged releases from repository

[Xavier Jurado via swift-dev]

I can confirm that both issues were solved/bypassed by rebuilding the
toolchain with assertions disabled. The provided examples compiled
successfully, so we finally got the same result as the official 2.2
toolchain.

Thank you again for the input!

2016-10-06 9:26 GMT+02:00 Xavier Jurado :

> Thanks for the hint! When I built the toolchain I modified the
> "mixin_lightweight_assertions" preset locally to use "no-assertions" and
> "swift-assertions", thinking it was the appropriate combination based on a
> FIXME comment. I will try building it again with only "no-assertions" and
> report back.
>
> 2016-10-05 18:28 GMT+02:00 Jordan Rose :
>
>> Aha, so the second bug is because home-built toolchains have assertions
>> on by default and Xcode GM toolchains generally have them off. (Not a
>> promise, but true of the last few Xcodes.) Of course, if you hit an
>> assertion failure, there’s no telling what the no-asserts build is actually
>> doing.
>>
>> I’m not so sure the first bug falls into the same category yet, but it
>> might as well.
>>
>> Jordan
>>
>>
>> > On Oct 4, 2016, at 14:05, Jordan Rose via swift-dev <
>> swift-dev@swift.org> wrote:
>> >
>> > Thanks, Xavi. Hopefully these aren't blocking you in Xcode 8 either (in
>> either Swift 2.3 or Swift 3).
>> >
>> >> On Oct 4, 2016, at 8:03, Xavier Jurado via swift-dev <
>> swift-dev@swift.org> wrote:
>> >>
>> >> Hello Jordan,
>> >>
>> >> We have filled two bugs against bugs.swift.org to document two crashes
>> >> that are only reproducible with our toolchain built from the
>> >> swift-2.2.1-RELEASE tag, but that appear fixed in the official
>> >> toolchain bundled with Xcode 7.3.1 (7D1014).
>> >>
>> >> Crashers:
>> >>
>> >> https://bugs.swift.org/browse/SR-2844
>> >> https://bugs.swift.org/browse/SR-2845
>> >>
>> >> Since using the official toolchain somehow fixes the issues we realize
>> >> they are far from critical, but we have reported them in hope of
>> >> finding the discrepancies between the official toolchain and the the
>> >> tagged releases.
>> >>
>> >> Thanks,
>> >> Xavi
>> >> ___
>> >> swift-dev mailing list
>> >> swift-dev@swift.org
>> >> https://lists.swift.org/mailman/listinfo/swift-dev
>> >
>> > ___
>> > swift-dev mailing list
>> > swift-dev@swift.org
>> > https://lists.swift.org/mailman/listinfo/swift-dev
>>
>>
>
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Differences between Xcode official toolchains and tagged releases from repository

[Jordan Rose via swift-dev]

Aha, so the second bug is because home-built toolchains have assertions on by 
default and Xcode GM toolchains generally have them off. (Not a promise, but 
true of the last few Xcodes.) Of course, if you hit an assertion failure, 
there’s no telling what the no-asserts build is actually doing.

I’m not so sure the first bug falls into the same category yet, but it might as 
well.

Jordan


> On Oct 4, 2016, at 14:05, Jordan Rose via swift-dev  
> wrote:
> 
> Thanks, Xavi. Hopefully these aren't blocking you in Xcode 8 either (in 
> either Swift 2.3 or Swift 3).
> 
>> On Oct 4, 2016, at 8:03, Xavier Jurado via swift-dev  
>> wrote:
>> 
>> Hello Jordan,
>> 
>> We have filled two bugs against bugs.swift.org to document two crashes
>> that are only reproducible with our toolchain built from the
>> swift-2.2.1-RELEASE tag, but that appear fixed in the official
>> toolchain bundled with Xcode 7.3.1 (7D1014).
>> 
>> Crashers:
>> 
>> https://bugs.swift.org/browse/SR-2844
>> https://bugs.swift.org/browse/SR-2845
>> 
>> Since using the official toolchain somehow fixes the issues we realize
>> they are far from critical, but we have reported them in hope of
>> finding the discrepancies between the official toolchain and the the
>> tagged releases.
>> 
>> Thanks,
>> Xavi
>> ___
>> swift-dev mailing list
>> swift-dev@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-dev
> 
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Differences between Xcode official toolchains and tagged releases from repository

[Xavier Jurado via swift-dev]

Hello Jordan,

We have filled two bugs against bugs.swift.org to document two crashes
that are only reproducible with our toolchain built from the
swift-2.2.1-RELEASE tag, but that appear fixed in the official
toolchain bundled with Xcode 7.3.1 (7D1014).

Crashers:

https://bugs.swift.org/browse/SR-2844
https://bugs.swift.org/browse/SR-2845

Since using the official toolchain somehow fixes the issues we realize
they are far from critical, but we have reported them in hope of
finding the discrepancies between the official toolchain and the the
tagged releases.

Thanks,
Xavi
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Differences between Xcode official toolchains and tagged releases from repository

[Jordan Rose via swift-dev]

Yes, there are sometimes internal-only changes in the Xcode toolchains, but I 
wouldn't expect those to have different behavior around succeeding or failing a 
simple compile. Can you provide any more information? Any custom build process 
you've set up?

Jordan


> On Oct 3, 2016, at 3:34, Daniel Martín via swift-dev  
> wrote:
> 
> Hello, all:
> 
> Is there any difference between the official toolchains included with Xcode 
> and the tagged releases from the repository? Maybe the Xcode team is using 
> some special flags for compilation or applying internal fixes? I ask this 
> question because we're seeing some projects that compile fine with the 
> official toolchain, but fail to do so with one downloaded from the 
> repository, from the exact tagged version.
> 
> Before we investigate this further, is it possible to create an "official" 
> Swift toolchain using the build scripts (for internal use, I assume we cannot 
> upload to the Store with that toolchain)? Does the Xcode team generate the 
> binaries from the repository tags?
> 
> Thanks,
> Daniel Martín
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Differences between Xcode official toolchains and tagged releases from repository

[mishal_shah via swift-dev]

> On Oct 3, 2016, at 7:51 AM, Zhao Xin via swift-dev  
> wrote:
> 
> I think if you want to upload your apps to App Store, you will need the 
> toolchain together with Xcode. Also, playground should only work with that 
> toolchain.
The toolchain from swift.org should work with playground, if it does not please 
file bug on bugs.swift.org. 

Info from swift.org: 

"To submit to the App Store you must build your app using the version of Swift 
that comes included within Xcode.” 
https://swift.org/download/#using-downloads

Thanks,
Mishal Shah

> 
> Zhaoxin
> 
> On Mon, Oct 3, 2016 at 6:34 PM, Daniel Martín via swift-dev 
> > wrote:
> Hello, all:
> 
> Is there any difference between the official toolchains included with Xcode 
> and the tagged releases from the repository? Maybe the Xcode team is using 
> some special flags for compilation or applying internal fixes? I ask this 
> question because we're seeing some projects that compile fine with the 
> official toolchain, but fail to do so with one downloaded from the 
> repository, from the exact tagged version.
> 
> Before we investigate this further, is it possible to create an "official" 
> Swift toolchain using the build scripts (for internal use, I assume we cannot 
> upload to the Store with that toolchain)? Does the Xcode team generate the 
> binaries from the repository tags?
> 
> Thanks,
> Daniel Martín
> 
> ___
> swift-dev mailing list
> swift-dev@swift.org 
> https://lists.swift.org/mailman/listinfo/swift-dev 
> 
> 
> 
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] Differences between Xcode official toolchains and tagged releases from repository

[Zhao Xin via swift-dev]

I think if you want to upload your apps to App Store, you will need the
toolchain together with Xcode. Also, playground should only work with that
toolchain.

Zhaoxin

On Mon, Oct 3, 2016 at 6:34 PM, Daniel Martín via swift-dev <
swift-dev@swift.org> wrote:

> Hello, all:
>
> Is there any difference between the official toolchains included with
> Xcode and the tagged releases from the repository? Maybe the Xcode team is
> using some special flags for compilation or applying internal fixes? I ask
> this question because we're seeing some projects that compile fine with the
> official toolchain, but fail to do so with one downloaded from the
> repository, from the exact tagged version.
>
> Before we investigate this further, is it possible to create an "official"
> Swift toolchain using the build scripts (for internal use, I assume we
> cannot upload to the Store with that toolchain)? Does the Xcode team
> generate the binaries from the repository tags?
>
> Thanks,
> Daniel Martín
>
> ___
> swift-dev mailing list
> swift-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
>
>
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] Differences between Xcode official toolchains and tagged releases from repository

[Daniel Martín via swift-dev]

Hello, all:
Is there any difference between the official toolchains included with Xcode and 
the tagged releases from the repository? Maybe the Xcode team is using some 
special flags for compilation or applying internal fixes? I ask this question 
because we're seeing some projects that compile fine with the official 
toolchain, but fail to do so with one downloaded from the repository, from the 
exact tagged version.
Before we investigate this further, is it possible to create an "official" 
Swift toolchain using the build scripts (for internal use, I assume we cannot 
upload to the Store with that toolchain)? Does the Xcode team generate the 
binaries from the repository tags?
Thanks,
Daniel Martín___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev