Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Remove "powerpc64le" and "mipsel" target_arch #31312

Merged
merged 1 commit into from
Feb 2, 2016

Conversation

alexcrichton
Copy link
Member

Currently the mipsel-unknown-linux-gnu target doesn't actually set the
target_arch value to mipsel but it rather uses mips. Alternatively the
powerpc64le target does indeed set the target_arch as powerpc64le,
causing a bit of inconsistency between theset two.

As these are just the same instance of one instruction set, let's use
target_endian to switch between them and only set the target_arch as one
value. This should cut down on the number of #[cfg] annotations necessary and
all around be a little more ergonomic.

@rust-highfive
Copy link
Contributor

r? @aturon

(rust_highfive has picked a reviewer for you, use r? to override)

@alexcrichton
Copy link
Member Author

r? @brson

There was a little discussion which led to this conclusion, and I believe this is not a breaking change because mipsel was never actually generated and powerpc64le is nightly only right now.

cc @antonblanchard

@rust-highfive rust-highfive assigned brson and unassigned aturon Jan 30, 2016
@brson
Copy link
Contributor

brson commented Feb 2, 2016

@bors r+

@bors
Copy link
Collaborator

bors commented Feb 2, 2016

📌 Commit 4c4ab1d has been approved by brson

@bors
Copy link
Collaborator

bors commented Feb 2, 2016

⌛ Testing commit 4c4ab1d with merge 20b6b58...

@bors
Copy link
Collaborator

bors commented Feb 2, 2016

💔 Test failed - auto-linux-64-nopt-t

Currently the `mipsel-unknown-linux-gnu` target doesn't actually set the
`target_arch` value to `mipsel` but it rather uses `mips`. Alternatively the
`powerpc64le` target does indeed set the `target_arch` as `powerpc64le`,
causing a bit of inconsistency between theset two.

As these are just the same instance of one instruction set, let's use
`target_endian` to switch between them and only set the `target_arch` as one
value. This should cut down on the number of `#[cfg]` annotations necessary and
all around be a little more ergonomic.
@alexcrichton
Copy link
Member Author

🎵 Where in the world, is, Carmen Sandiego? 🎵

@bors: r+ 8f803c2

@bors
Copy link
Collaborator

bors commented Feb 2, 2016

⌛ Testing commit 8f803c2 with merge 2dc132e...

bors added a commit that referenced this pull request Feb 2, 2016
Currently the `mipsel-unknown-linux-gnu` target doesn't actually set the
`target_arch` value to `mipsel` but it rather uses `mips`. Alternatively the
`powerpc64le` target does indeed set the `target_arch` as `powerpc64le`,
causing a bit of inconsistency between theset two.

As these are just the same instance of one instruction set, let's use
`target_endian` to switch between them and only set the `target_arch` as one
value. This should cut down on the number of `#[cfg]` annotations necessary and
all around be a little more ergonomic.
@bors bors merged commit 8f803c2 into rust-lang:master Feb 2, 2016
@alexcrichton alexcrichton deleted the no-le-in-powerpc64le branch February 8, 2016 23:59
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants