Skip to content
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

[SR-14282] Compiler crash in DictionaryTrapsObjC.swift #56641

Closed
benrimmington opened this issue Feb 27, 2021 · 3 comments
Closed

[SR-14282] Compiler crash in DictionaryTrapsObjC.swift #56641

benrimmington opened this issue Feb 27, 2021 · 3 comments
Assignees
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself

Comments

@benrimmington
Copy link
Collaborator

Previous ID SR-14282
Radar rdar://problem/74877200
Original Reporter @benrimmington
Type Bug
Status Closed
Resolution Cannot Reproduce
Environment
  • macOS 11.2.1 (20D74)

  • Xcode 12.4 (12D4e)

  • main branch of apple/swift

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug
Assignee @benrimmington
Priority Medium

md5: d52ffd6be17508cc749f70bd8e9b6837

Issue Description:

There are three ForcedVerbatimBridge validation-tests in DictionaryTrapsObjC.swift, which crash when compiling with optimizations.

The entire test file was previously disabled, and the three tests will now be disabled with #if DEBUG.

Stack dump:
0.  Program arguments: /Users/benrimmington/Public/apple/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/bin/swift-frontend -frontend -c -primary-file /Users/benrimmington/Public/apple/swift/validation-test/stdlib/DictionaryTrapsObjC.swift -target x86_64-apple-macosx10.9 -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -F /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -F /Users/benrimmington/Public/apple/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/lib -module-cache-path /Users/benrimmington/Public/apple/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/swift-test-results/x86_64-apple-macosx10.9/clang-module-cache -swift-version 4 -O -ignore-module-source-info -target-sdk-version 11.1 -module-name main -o /var/folders/n7/mq4lxxk13cq8ptrk4sn55khc0000gn/T/DictionaryTrapsObjC-b4dec4.o
1.  Swift version 5.4-dev (LLVM 2ca842e25f65b93, Swift 42a227abc3ef6ea)
2.  While evaluating request ExecuteSILPipelineRequest(Run pipelines { Mandatory Diagnostic Passes + Enabling Optimization Passes } on SIL for main.main)
3.  While running pass #​0 SILModuleTransform "SILGenCleanup".
Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0  swift-frontend           0x0000000111ee82e7 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 39
1  swift-frontend           0x0000000111ee7505 llvm::sys::RunSignalHandlers() + 85
2  swift-frontend           0x0000000111ee8906 SignalHandler(int) + 262
3  libsystem_platform.dylib 0x00007fff2063dd7d _sigtramp + 29
4  libsystem_platform.dylib 000000000000000000 _sigtramp + 18446603339972747936
5  swift-frontend           0x000000010e1890ab swift::CanonicalizeInstruction::canonicalize(swift::SILInstruction*) + 2827
6  swift-frontend           0x000000010e003c14 (anonymous namespace)::SILGenCleanup::run() + 628
7  swift-frontend           0x000000010e019b7e swift::SILPassManager::runModulePass(unsigned int) + 702
8  swift-frontend           0x000000010e02002a swift::SILPassManager::execute() + 666
9  swift-frontend           0x000000010e016558 swift::SILPassManager::executePassPipelinePlan(swift::SILPassPipelinePlan const&) + 72
10 swift-frontend           0x000000010e0164f3 swift::ExecuteSILPipelineRequest::evaluate(swift::Evaluator&, swift::SILPipelineExecutionDescriptor) const + 51
11 swift-frontend           0x000000010e03ad8d swift::SimpleRequest<swift::ExecuteSILPipelineRequest, std::__1::tuple<> (swift::SILPipelineExecutionDescriptor), (swift::RequestFlags)1>::evaluateRequest(swift::ExecuteSILPipelineRequest const&, swift::Evaluator&) + 29
12 swift-frontend           0x000000010e022670 llvm::Expected<swift::ExecuteSILPipelineRequest::OutputType> swift::Evaluator::getResultUncached<swift::ExecuteSILPipelineRequest>(swift::ExecuteSILPipelineRequest const&) + 240
13 swift-frontend           0x000000010e016784 swift::executePassPipelinePlan(swift::SILModule*, swift::SILPassPipelinePlan const&, bool, swift::irgen::IRGenModule*) + 68
14 swift-frontend           0x000000010e024997 swift::runSILDiagnosticPasses(swift::SILModule&) + 87
15 swift-frontend           0x000000010d8434dc swift::CompilerInstance::performSILProcessing(swift::SILModule*) + 60
16 swift-frontend           0x000000010d728659 performCompileStepsPostSILGen(swift::CompilerInstance&, std::__1::unique_ptr<swift::SILModule, std::__1::default_delete<swift::SILModule> >, llvm::PointerUnion<swift::ModuleDecl*, swift::SourceFile*>, swift::PrimarySpecificPaths const&, int&, swift::FrontendObserver*) + 633
17 swift-frontend           0x000000010d72809e performCompileStepsPostSema(swift::CompilerInstance&, int&, swift::FrontendObserver*) + 350
18 swift-frontend           0x000000010d71d515 swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 4885
19 swift-frontend           0x000000010d6b7717 main + 519
20 libdyld.dylib            0x00007fff20614621 start + 1
21 libdyld.dylib            0x000000000000001a start + 18446603339972917754
<unknown>:0: error: unable to execute command: Segmentation fault: 11
<unknown>:0: error: compile command failed due to signal 11 (use -v to see invocation)

--
@typesanitizer
Copy link

@swift-ci create

@eeckstein
Copy link
Member

@benrimmington I cannot reproduce this. Did you try with top of main? Any build-script options you used?

@benrimmington
Copy link
Collaborator Author

I cannot reproduce this.

@@eeckstein Neither can I now. I've created apple/swift#36426 to remove the DEBUG-only restriction.

Did you try with top of main?

I would have used top of main, 3 weeks ago, for apple/swift#36072.

Any build-script options you used?

I would probably have started with
utils/build-script --clean --release-debuginfo --test,
followed by utils/run-test.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself
Projects
None yet
Development

No branches or pull requests

3 participants