i128 is being stabilized#235
Conversation
| #![feature(compiler_builtins)] | ||
| #![feature(core_intrinsics)] | ||
| #![feature(naked_functions)] | ||
| #![feature(i128_type)] |
There was a problem hiding this comment.
You'd most likely have to do #[cfg_attr(stage0, feature(i128_type))] here, as on stage0 it is still needed.
There was a problem hiding this comment.
Hmm... It seemed to work fine when I made this change locally?
|
Thanks! I think it's ok if this is here, right? Does this fail the build? |
|
(in that I'd prefer to land the rustc change first and then land the change here after that's gone through) |
|
It's sort of a deadlock. Rustc fails without this, but this fails without rustc. |
|
The "failure" I think is |
|
Yeah I think that's the best solution. If we want we can re-add if after the rustc change goes through. |
|
Moving the |
|
We could use the old external tool update workflow here:
|
|
That's what I originally suggested in the rustc PR but just ignoring the warning temporarily seems easier. |
|
Umm... does anyone understand the current Travis failure: |
|
It looks like the current change in the PR might be sufficient if we fix the build failures... alternately, I could do @kennytm's suggestion. Just let me know :) |
|
Ok this strategy seems fine by me yeah |
|
Hmm... this doesn't seem to have worked... I don't understand why. |
| #![feature(abi_unadjusted)] | ||
| #![feature(linkage)] | ||
| #![feature(lang_items)] | ||
| #![allow(unused_features)] |
There was a problem hiding this comment.
Oh this is #![allow(unused_features)], but you need #[allow(stable_features)].
cc rust-lang/rust#35118 rust-lang/rust#49101