Could you try using cargo-bisect-rustc to narrow the introduction of the issue to a particular nightly? If you can do that, that should make it easy to pinpoint the introduction of the problem. (Unless it turns out that there's an LLVM version bump in that timeframe.)