-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Move swift runtime failure messages from linkage name to function name #29506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@swift-ci test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Build failed |
Build failed |
@@ -1864,7 +1864,7 @@ void IRGenDebugInfoImpl::addFailureMessageToCurrentLoc(IRBuilder &Builder, | |||
FuncName += failureMsg; | |||
|
|||
llvm::DISubprogram *TrapSP = DBuilder.createFunction( | |||
MainModule, StringRef(), FuncName, TrapLoc->getFile(), 0, DIFnTy, 0, | |||
MainModule, FuncName, StringRef(), TrapLoc->getFile(), 0, DIFnTy, 0, | |||
llvm::DINode::FlagArtificial, llvm::DISubprogram::SPFlagDefinition, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please also add a testcase to test/DebugInfo ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the original tests (test/DebugInfo/linetable-codeview.swift
& test/IRGen/condfail_message.swift
) to reflect my changes.
Should I add another test ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, that is fine! For some reason I didn't see this earlier.
Signed-off-by: Med Ismail Bennani <[email protected]>
@swift-ci test |
This PR moves swift runtimes failure (#25978) messages from the linkage name to the function name.
Since the failure message (i.e.
Swift runtime failure: arithmetic overflow
) don't conform with a proper mangling, when lldb tries to fetch the inlined frame symbol, it gets discarded. Moving it to the function name fixes this issue.Signed-off-by: Med Ismail Bennani [email protected]