[swift-dev] DebugScope Verification Error

2018-01-15 Thread Raj Barik via swift-dev
Hi, I am running into a debug scope SIL Verifier error when creating a new function (NF) from an existing one (F). Can someone point me where I am going wrong? NF = M.createFunction(, F->getDebugScope()); SILBasicBlock *NFBody = NF->createBasicBlock(); SILBuilder NFBuilder(NFBody); SILOpenedA

Re: [swift-dev] DebugScope Verification Error

2018-01-15 Thread Mark Lacey via swift-dev
I’d suggest looking at SILCloner.h as well as ScopeCloner in SILBasicBlock.cpp to see how they are dealing with debug scopes. Mark > On Jan 15, 2018, at 9:24 AM, Raj Barik via swift-dev > wrote: > > Hi, > > I am running into a debug scope SIL Verifier error when creating a new > function (N

Re: [swift-dev] State of String: ABI & Performance

2018-01-15 Thread Bob Wilson via swift-dev
> On Jan 11, 2018, at 9:46 PM, Chris Lattner via swift-dev > wrote: > >>> >>> Finally, what tradeoffs do you see between a 1-word vs 2-word string? Are >>> we really destined to have 2-words? That’s still much better than the 3 >>> words we have now, but for some workloads it is a signifi

Re: [swift-dev] DebugScope Verification Error

2018-01-15 Thread Raj Barik via swift-dev
Mark, Thanks a lot for quick reply. Is there any reason this interface in SILInstruction should be private? void setDebugScope(SILBuilder &B, const SILDebugScope *DS); In my case, I am splicing the old F into the new function NF. While splicing retains the debug scope, the new instruction (InitR

Re: [swift-dev] DebugScope Verification Error

2018-01-15 Thread Mark Lacey via swift-dev
> On Jan 15, 2018, at 12:54 PM, Raj Barik wrote: > > Mark, > > Thanks a lot for quick reply. > > Is there any reason this interface in SILInstruction should be private? > void setDebugScope(SILBuilder &B, const SILDebugScope *DS); > > In my case, I am splicing the old F into the new functio

Re: [swift-dev] DebugScope Verification Error

2018-01-15 Thread Raj Barik via swift-dev
Thanks Mark. You are right, the following assertion fails require(!DS || DS->getParentFunction() == I->getFunction(), "debug scope of instruction belongs to a different function"); I am not sure if we need such a check. On Mon, Jan 15, 2018 at 4:16 PM, Mark Lacey wrote: > > > On Ja

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

2018-01-15 Thread Kuba Mracek via swift-dev
java.io.IOException: No space left on device Kuba Sent from my iPhone > On Jan 15, 2018, at 5:46 PM, swift...@swift.org wrote: > > [FAILURE] oss-swift-5.0-incremental-RA-linux-ubuntu-16_04 [#44] > > Build URL: > https://ci.swift.org/job/oss-swift-5.0-incremental-RA-linux-ubuntu-16_04/44/ >

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 - Long Test (master-llvm-swift5-transition) #34

2018-01-15 Thread Kuba Mracek via swift-dev
fatal error: error in backend: IO failure on output stream: No space left on device Kuba Sent from my iPhone > On Jan 15, 2018, at 6:48 PM, swift...@swift.org wrote: > > [FAILURE] > oss-swift-master-llvm-swift5-transition-incremental-RA-linux-ubuntu-16_04-long-test > [#34] > > Build URL:

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 - Long Test (master-llvm-swift5-transition) #34

2018-01-15 Thread Mishal Shah via swift-dev
Fixed. Thanks, Mishal Shah > On Jan 15, 2018, at 6:56 PM, Kuba Mracek wrote: > > fatal error: error in backend: IO failure on output stream: No space left on > device > > Kuba > > Sent from my iPhone > > On Jan 15, 2018, at 6:48 PM, swift...@swift.org > wrote: >