Skip to content

cmd/link, runtime: add initial cgo support for ppc64 #28546

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

Closed
wants to merge 1 commit into from

Conversation

zte-majiang
Copy link
Contributor

@zte-majiang zte-majiang commented Nov 2, 2018

We should be able to build docker after this get applied.

Updates #13192

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

@googlebot googlebot added the cla: no Used by googlebot to label PRs as having an invalid CLA. The text of this label should not change. label Nov 2, 2018
@googlebot
Copy link

CLAs look good, thanks!

@googlebot googlebot added cla: yes Used by googlebot to label PRs as having a valid CLA. The text of this label should not change. and removed cla: no Used by googlebot to label PRs as having an invalid CLA. The text of this label should not change. labels Nov 2, 2018
@gopherbot
Copy link
Contributor

This PR (HEAD: 5b1ff45) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/146898 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gerrit User 5976:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gerrit User 15676:

Patch Set 1:

Do we really want to be putting our function descriptors in .text? I guess for static linking (and without static PIE) it's fine, but might be better to put it in .data.rel.ro, if not .opd?


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gerrit User 5206:

Patch Set 1:

(2 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gerrit User 6320:

Patch Set 1:

(3 comments)

Patch Set 1:

Do we really want to be putting our function descriptors in .text? I guess for static linking (and without static PIE) it's fine, but might be better to put it in .data.rel.ro, if not .opd?

I think it would be best to be consistent with other ppc64 compilers and put them in the .opd.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gerrit User 6320:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gerrit User 29664:

Patch Set 1:

(5 comments)

Patch Set 1:

(3 comments)

Patch Set 1:

Do we really want to be putting our function descriptors in .text? I guess for static linking (and without static PIE) it's fine, but might be better to put it in .data.rel.ro, if not .opd?

I think it would be best to be consistent with other ppc64 compilers and put them in the .opd.

Shall we fix the problem in this patch?


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 8c8173a) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/146898 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gerrit User 12446:

Uploaded patch set 2: Commit message was updated.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: d2512b9) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/146898 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gerrit User 29664:

Patch Set 3: Code-Review+1

Hi, I have updated the patch a few days ago. It is ok now?


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gerrit User 6320:

Patch Set 3:

(5 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gerrit User 6320:

Patch Set 3:

You might want to also look at what tests in cmd/dist/test.go that are current disabled for linux/ppc64 that could be enabled with this change.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ian Lance Taylor:

Patch Set 3:

Please update the commit message as I requested earlier. Thanks.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Jiang Ma:

Patch Set 3:

Patch Set 3:

Please update the commit message as I requested earlier. Thanks.

Hi, I'm sorry but I have changed the commit message on github(see d2512b9).
It looks like the GerritBot did not pull the message changes(see https://go-review.googlesource.com/c/go/+/146898/3//COMMIT_MSG#4).
What should I do, if I want to correct the commit message here?


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ian Lance Taylor:

Patch Set 3:

Please update the commit message as I requested earlier. Thanks.

Hi, I'm sorry but I have changed the commit message on github(see d2512b9).
It looks like the GerritBot did not pull the message changes(see https://go-review.googlesource.com/c/go/+/146898/3//COMMIT_MSG#4).
What should I do, if I want to correct the commit message here?

You need to edit the title and first comment of the Github pull request at #28546 . Thanks.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@zte-majiang zte-majiang changed the title cgo: add initial support for ppc64 cmd/link, runtime: add initial cgo support for ppc64 Nov 11, 2018
@gopherbot
Copy link
Contributor

Message from Jiang Ma:

Patch Set 4:

(3 comments)

Patch Set 3:

Please update the commit message as I requested earlier. Thanks.

Hi, I'm sorry but I have changed the commit message on github(see d2512b9).
It looks like the GerritBot did not pull the message changes(see https://go-review.googlesource.com/c/go/+/146898/3//COMMIT_MSG#4).
What should I do, if I want to correct the commit message here?

You need to edit the title and first comment of the Github pull request at #28546 . Thanks.

Thanks, It's OK now :)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Clément Chigot:

Patch Set 4:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lynn Boger:

Patch Set 4:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

This PR (HEAD: 888df3f) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/146898 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

This PR (HEAD: ce7068b) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/146898 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Jiang Ma:

Patch Set 6: Code-Review+1

(2 comments)

Patch Set 3:

You might want to also look at what tests in cmd/dist/test.go that are current disabled for linux/ppc64 that could be enabled with this change.

Thanks for the advice. I have take a quick look at cmd/dist/test.go, it seems that the change is not as easy as I expected.
As our final goal is to make ppc64 support most features of ppc64le(such as cgo), I think we could do it step by step. Let's try to enable tests next time, shall we?


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lynn Boger:

Patch Set 6:

Patch Set 6: Code-Review+1

(2 comments)

Patch Set 3:

You might want to also look at what tests in cmd/dist/test.go that are current disabled for linux/ppc64 that could be enabled with this change.

Thanks for the advice. I have take a quick look at cmd/dist/test.go, it seems that the change is not as easy as I expected.
As our final goal is to make ppc64 support most features of ppc64le(such as cgo), I think we could do it step by step. Let's try to enable tests next time, shall we?

That's fine. After looking further, I can see it is more complicated that I thought.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Jiang Ma:

Patch Set 6:

(1 comment)

Patch Set 4:

(1 comment)
It this OK for AIX?


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Clément Chigot:

Patch Set 6:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

We should be able to build docker after this get applied.

Updates golang#13192
@gopherbot
Copy link
Contributor

This PR (HEAD: 210b7bc) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/146898 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Jiang Ma:

Patch Set 7: Code-Review+1

(1 comment)

Hi all,
I have fix all the problems. Is this patch OK for everyone now?


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Clément Chigot:

Patch Set 7: Code-Review+1

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Tobias Klauser:

Patch Set 7: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 7:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=af7630f1


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 7: TryBot-Result+1

TryBots are happy.


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lynn Boger:

Patch Set 7:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Clément Chigot:

Patch Set 7:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lynn Boger:

Patch Set 7:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lynn Boger:

Patch Set 7: Code-Review+2


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Lynn Boger:

Patch Set 7: Run-TryBot+1


Please don’t reply on this GitHub thread. Visit golang.org/cl/146898.
After addressing review feedback, remember to publish your drafts!

gopherbot pushed a commit that referenced this pull request Nov 20, 2018
We should be able to build docker after this get applied.

Updates #13192

Change-Id: I5378d3518fac52d6bd4c97828884c1b382b7ace5
GitHub-Last-Rev: 210b7bc
GitHub-Pull-Request: #28546
Reviewed-on: https://go-review.googlesource.com/c/146898
Reviewed-by: Jiang Ma <[email protected]>
Reviewed-by: Clément Chigot <[email protected]>
Reviewed-by: Lynn Boger <[email protected]>
Run-TryBot: Tobias Klauser <[email protected]>
Run-TryBot: Lynn Boger <[email protected]>
TryBot-Result: Gobot Gobot <[email protected]>
@gopherbot
Copy link
Contributor

This PR is being closed because golang.org/cl/146898 has been merged.

@gopherbot gopherbot closed this Nov 20, 2018
bradfitz pushed a commit that referenced this pull request Nov 21, 2018
We should be able to build docker after this get applied.

Updates #13192

Change-Id: I5378d3518fac52d6bd4c97828884c1b382b7ace5
GitHub-Last-Rev: 210b7bc
GitHub-Pull-Request: #28546
Reviewed-on: https://go-review.googlesource.com/c/146898
Reviewed-by: Jiang Ma <[email protected]>
Reviewed-by: Clément Chigot <[email protected]>
Reviewed-by: Lynn Boger <[email protected]>
Run-TryBot: Tobias Klauser <[email protected]>
Run-TryBot: Lynn Boger <[email protected]>
TryBot-Result: Gobot Gobot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Used by googlebot to label PRs as having a valid CLA. The text of this label should not change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants