-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Reland (#120419):[Exegesis][RISCV] Add RISCV support for llvm-exegesis #120467
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
Conversation
This patch also makes following amendments to core exegesis: * Added distinction between regular registers aliasing check and registers used as memory address in instruction. * Added scratch memory space pointer register. * Added ability for targets to define register name to register number mapping (findRegisterByName). * General exegesis options were amended: * mattr - new option to pass a list of enabled target features * opcode-name - this option is amended to accept range of opcodes at once Llvm-exegesis RISCV port is a result of team effort. Below everyone involved listed. Co-authored-by: Konstantin Vladimirov <konstantin.vladimirov@syntacore.com> Co-authored-by: Dmitrii Petrov <dmitrii.petrov@syntacore.com> Co-authored-by: Dmitry Bushev <dmitry.bushev@syntacore.com> Co-authored-by: Mark Goncharov <mark.goncharov@syntacore.com> Co-authored-by: Anastasiya Chernikova <anastasiya.chernikova@syntacore.com>
@dybv-sc Thanks for the update! When I try out your patch, I am getting:
I'm guessing that |
Hi, Have you applied all of the patches there are in this request? We used to have this file, but after some discussion, we removed it (with the intention to rework and bring it back in some later request). Currently there should be no this file on top of our branch. |
RISCV_MC::isOpcodeAvailable) {} | ||
|
||
#define GET_REGISTER_MATCHER | ||
#include "RISCVGenAsmMatcher.inc" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be removed before relanding. It doesn't make sense to land with a forward fix already planned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, amended Kazu's fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please update the commit message before merging.
authored-by: Kazu Hirata <kazu@google.com>
3fe9d46
to
86f59cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Huh. When I applied Anyway, thank you for updating the patch! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks!
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/18/builds/8788 Here is the relevant piece of the build log for the reference
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/146/builds/1878 Here is the relevant piece of the build log for the reference
|
2nd reland attempt. This should be merged again and applying #120451 should fix buildbot issue.
Original commit message: