Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRegression: linking errors since latest nightly #34754
Comments
tomaka
changed the title
Regression: linking errors since last nightly
Regression: linking errors since latest nightly
Jul 10, 2016
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
After some investigation, the linking errors are the names of the five provided methods of the https://github.com/lifthrasiir/rust-encoding/blob/058aeac4c622337b97fce52e3ae34df5fb9451f1/src/types.rs#L192 And also these four functions as well: Interestingly, there are other chunks of code that are very similar (they implement (note: don't look at the EDIT: removed wrong stuff |
This comment has been minimized.
This comment has been minimized.
|
Couldn't reproduce on Linux. This is likely specific to MSVC. |
This comment has been minimized.
This comment has been minimized.
|
@tomaka Thanks that's all already very valuable information. It seems that you are compiling things with multiple codegen units. Does the error also occur if you with just one codegen unit? |
This comment has been minimized.
This comment has been minimized.
|
@michaelwoerister Good point, I had totally forgotten about codegen units. Compiling with |
This comment has been minimized.
This comment has been minimized.
|
@tomaka OK, that narrows the problem down somewhat. |
This comment has been minimized.
This comment has been minimized.
|
This comment has been minimized.
This comment has been minimized.
All the errors are the ones I linked above. The 5 default methods and the 4 methods of the trait implementation (of which only 1 overwrites a default method).
No. That's why I don't really know where to look for to find a repro. |
This comment has been minimized.
This comment has been minimized.
|
If you wish so I can also upload the project to a private location. |
This comment has been minimized.
This comment has been minimized.
|
@tomaka That would be helpful. |
michaelwoerister
self-assigned this
Jul 11, 2016
This comment has been minimized.
This comment has been minimized.
|
OK, I was able to reproduce this. It seems to have to do something with constants storing trait-objects ( |
This comment has been minimized.
This comment has been minimized.
|
Update |
This comment has been minimized.
This comment has been minimized.
|
triage: P-high |
rust-highfive
added
P-high
and removed
I-nominated
labels
Jul 21, 2016
This comment has been minimized.
This comment has been minimized.
|
I'll see that I'll take care of this next week. |
This comment has been minimized.
This comment has been minimized.
|
@mw status update? This will go to beta on 8/18. |
This comment has been minimized.
This comment has been minimized.
|
There were a few refactorings I needed to do before being able to fix this. These have landed by now, so I expect that the actual fix should be ready before beta. |
This comment has been minimized.
This comment has been minimized.
|
Sweet! |
This comment has been minimized.
This comment has been minimized.
|
Update from @rust-lang/compiler meeting: fix is in the queue, upping priority since this is a regression. |
bors
added a commit
that referenced
this issue
Aug 11, 2016
bors
added a commit
that referenced
this issue
Aug 12, 2016
bors
added a commit
that referenced
this issue
Aug 14, 2016
This comment has been minimized.
This comment has been minimized.
|
So, this should be fixed (via #35534) but there is no nightly containing the fix yet. |
This comment has been minimized.
This comment has been minimized.
|
OK, the latest nightly contains the fix. Could you please test whether it solves your problem? (and close the issue if it does) |
This comment has been minimized.
This comment has been minimized.
|
Thanks, seems to work! |
tomaka commentedJul 10, 2016
•
edited
Unfortunately I don't have any repro case, as my repro case is my big closed source project that I don't want to be public. Some other smaller projects of mine which use the same libraries and which I thought would trigger the same issue in fact do not trigger the same issue.
After some discussion on IRC, I decided to open an issue despite having no repro to show.
With the 2016-07-03 nightly (commit 696b703), the project compiles fine.
But with the 2016-07-08 nightly (commit 5e18b4b), I'm getting linking errors:
This is with the MSVC 64bits version of Rust.
According to IRC, the culprit is likely #33890