> On Nov 9, 2017, at 6:25 PM, Pavel Yaskevich <[email protected]> wrote: > > > >> On Nov 9, 2017, at 6:24 PM, Slava Pestov <[email protected] >> <mailto:[email protected]>> wrote: >> >> Relevant part of the change: >> >> https://github.com/apple/swift/pull/12787/commits/2a0cb060f8ad85f7b1bf1f6e77d82201ae4d0f2c#diff-36857e4a32f1cda824b3bf3cf60ae051L4072 >> >> <https://github.com/apple/swift/pull/12787/commits/2a0cb060f8ad85f7b1bf1f6e77d82201ae4d0f2c#diff-36857e4a32f1cda824b3bf3cf60ae051L4072> >> >> The function_ref or class_method for a method calls now comes after argument >> evaluation. > > Should it be fixed in LLDB or Swift?
I think it exposed an existing issue in Swift’s debug info emission. Slava >> >> Slava >> >>> On Nov 9, 2017, at 6:20 PM, Slava Pestov <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> I think it’s this change: >>> https://github.com/apple/swift/pull/12787/commits/2a0cb060f8ad85f7b1bf1f6e77d82201ae4d0f2c >>> >>> <https://github.com/apple/swift/pull/12787/commits/2a0cb060f8ad85f7b1bf1f6e77d82201ae4d0f2c> >>> >>> It caused some SIL instructions to be re-ordered in an equivalent way. >>> >> >
_______________________________________________ swift-lldb-dev mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-lldb-dev
