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-3474] Swift 3 Whole Module Optimization Issue #46062

swift-ci opened this issue Dec 22, 2016 · 2 comments

[SR-3474] Swift 3 Whole Module Optimization Issue #46062

swift-ci opened this issue Dec 22, 2016 · 2 comments


Copy link

swift-ci commented Dec 22, 2016

Previous ID SR-3474
Radar radar://29763639
Original Reporter jhzdev (JIRA User)
Type Bug

Attachment: Download


building with Xcode 8.2, running on iPhone 6 iOS 10

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug, OptimizedOnly, RunTimeCrash
Assignee None
Priority Medium

md5: 527562dfe02323edd05f58e89e529e0e

Issue Description:

I think I found a swift 3 whole module optimization issue. The code below, when building with release configuration and running on an iOS 10 real device, will always causes a crash.

import UIKit
class ViewController: UIViewController {
    override func viewDidLoad() {
        // Do any additional setup after loading the view.
        let orderby = "time"
        let url = "\(orderby)"
        Log("Request url: \(url)")
        if let url = URL(string: url) {
            let request = URLRequest(url: url)
    override func didReceiveMemoryWarning() {
        // Dispose of any resources that can be recreated.

func Log(_ log: String) {
    //    NSLog("%@", log)

You can see the attachment for more detail info.
Or if you use github, this is the repo:

Copy link
Collaborator Author

swift-ci commented Dec 23, 2016

Comment by Jun Z. (JIRA)

fix a typo

Copy link

gottesmm commented Jan 7, 2017

This is a dup of [SR-3301]. This was fixed in master in: 4282f35. Should be fixed in next release.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants