Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

update target json spec to match the one in-repo #396

Closed
wants to merge 1 commit into from

Conversation

steveklabnik
Copy link
Contributor

Found in #360 (comment)

@@ -174,19 +174,18 @@ Our target specification file now looks like this:

```json
{
"llvm-target": "x86_64-unknown-none",
"llvm-target": "x86_64-unknown-linux-gnu",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm not sure if this is correct or not; maybe the one in-repo needs to be updated to none?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the in-repo version should be none, seems like I missed this.

"disable-redzone": true,
"features": "-mmx,-sse,+soft-float"
"panic-strategy": "abort"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this diff is a little annoying, the only real change is the changes to linker/linker-flavor

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you keep the field order from the post and adjust the in-repo json file instead? (So that it is in the same order as it's introduced in the post)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i can do this, will adjust it soon

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants