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

clang needs -mprofile-kernel switch for ppc64le #1157

Closed
sm00th opened this issue Feb 9, 2021 · 5 comments
Closed

clang needs -mprofile-kernel switch for ppc64le #1157

sm00th opened this issue Feb 9, 2021 · 5 comments

Comments

@sm00th
Copy link
Contributor

sm00th commented Feb 9, 2021

During discussion in #1156 we found out that while it is possible to build a ppc64le kernel with clang, generated code is not kpatchable and clang needs an analog of gcc's -mprofile-kernel switch. @kamalesh-babulal is going to find out whether IBM's compiler team will be able to help us with that.

@jpoimboe
Copy link
Member

I presume we would also need a clang plugin similar to our gcc plugin to insert nops after local calls.

@kamalesh-babulal
Copy link
Contributor

I presume we would also need a clang plugin similar to our gcc plugin to insert nops after local calls.

I guess so, we might need a clang plugin variant too.

@kamalesh-babulal
Copy link
Contributor

Quick update: I had checked with the compiler team on two questions.

  1. If there is some alternative or undocumented switch in clang that's equal to that of gcc's -mprofile-kernel?
    clang lacks support for -mprofile-kernel equivalent.
  2. Is this any work planned or in progress to have such switch?
    There are no plans to add it in the near future. I update the issue, if there is some news on it.

@github-actions
Copy link

github-actions bot commented Aug 6, 2023

This issue has been open for 30 days with no activity and no assignee. It will be closed in 7 days unless a comment is added.

@github-actions github-actions bot added the stale label Aug 6, 2023
@github-actions
Copy link

This issue was closed because it was inactive for 7 days after being marked stale.

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

No branches or pull requests

3 participants