Re: [swift-dev] Purpose of validation-test/Reflection/reflect_*.swift

on Wed Oct 26 2016, Slava Pestov wrote: > The tests are there to ensure the reflection output doesn’t > accidentally break or change. Unless you have reason to think it will break or change *only* for some particular stdlib types, and that reflecting the implementation details of those types i

Re: [swift-dev] Stack dump of the compiler?

> set_target_properties(${swift_binaries} properties ENABLE_EXPORTS 1) ? > I don't know if it's this simple though. Yeah, that should work as well. But, I'm not sure which tools should be `ENABLE_EXPORT`ed. 2016-10-27 3:04 GMT+09:00 Flamedoge : > > Do not add flags to export symbols from execu

Re: [swift-dev] Purpose of validation-test/Reflection/reflect_*.swift

The tests are there to ensure the reflection output doesn’t accidentally break or change. However if you’re updating the layout of those types you need to update the tests. Slava > On Oct 26, 2016, at 5:41 PM, Michael Gottesman via swift-dev > wrote: > > >> On Oct 26, 2016, at 5:29 PM, Alex

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

This issue has been fixed. Please ignore. > On Oct 26, 2016, at 6:38 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-16_04 [#408] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_04/408/ >

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

Thanks! Should be fixed now. Anna. > On Oct 26, 2016, at 6:09 PM, mishal_shah > wrote: > > Hi Anna, > > Can you please look at this error? > > /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/llvm/projects/compiler-rt/lib/sanitizer_com

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (master) #8125

Incremental build error or actual duplicate symbol? lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cc.o: In function `__sanitizer::FindAvailableMemoryRange(unsigned long, unsigned long, unsigned long)': /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linu

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

Hi Anna, Can you please look at this error? /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_posix.cc:362: multiple definition of `__sanitizer::FindAvailableMemoryRange(unsigned long, unsigned long, unsigned

Re: [swift-dev] Purpose of validation-test/Reflection/reflect_*.swift

> On Oct 26, 2016, at 5:29 PM, Alexis via swift-dev wrote: > > I’m not clear on what the reflection tests are attempting to actually verify. > Just that we don’t change the internal layout of these types accidentally? > We’re churning up the layouts of a lot of the collections to get things al

[swift-dev] Purpose of validation-test/Reflection/reflect_*.swift

I’m not clear on what the reflection tests are attempting to actually verify. Just that we don’t change the internal layout of these types accidentally? We’re churning up the layouts of a lot of the collections to get things all set up for ABI stability, which means mechanically updating these t

Re: [swift-dev] problems building swift-3.0-RELEASE

Sorry this was user error. Somehow I didn't have either llvm or clang checked out to swift-3.0-RELEASE before I started the build. It would be great if update-checkout were changed to run 'git pull --tags', I think. I tried adding it to the script myself but I got some obscure git error. On

Re: [swift-dev] Stack dump of the compiler?

> Do not add flags to export symbols from executables without the ENABLE_EXPORTS target property. set_target_properties(${swift_binaries} properties ENABLE_EXPORTS 1) ? I don't know if it's this simple though