This patch enables support for Cortex-A510 CPUs.
Details
Diff Detail
Event Timeline
As I did the downstream work for this, I'm happy with it to go in in this form.
This doesn't seem.. wise. Please make sure the reviews you do are at a sufficient quality, and it is probably best not to review patches you write yourself.
llvm/include/llvm/Support/AArch64TargetParser.def | ||
---|---|---|
179 | Why is this 8.3? The TRM (https://developer.arm.com/documentation/101604/0003/The-Cortex-A510--core) describes it as implementing the 9.0-A architecture. | |
llvm/lib/Target/AArch64/AArch64.td | ||
1055 | This should be in some sort of order, next to the Cortex-A55. It should probably be called ProcA510 for consistency too. | |
1214 | Ordering. Please use the CortexA55Model. This is not an out of order core like the A57. | |
llvm/lib/Target/AArch64/AArch64Subtarget.cpp | ||
196 | This can be the same case block as the A53 and A55. |
Very good point!
I reduce this to the claim that it has been stable downstream for a couple of weeks now.
Yeah, those changes are in history, But we need them in the present to commit :)
The patch is incorrectly updated, did you followed https://llvm.org/docs/Phabricator.html#requesting-a-review-via-the-command-line?
@xgupta I followed the request review via web interface section of that page. Let me look into it.
It misses llvm/test/CodeGen/AArch64 and llvm/test/MC/AArch64 testcases changes, see for example https://reviews.llvm.org/D36667 (Cortex-A55 support).
I'm not convinced this is required - those tests are to ensure that the extensions (rcpc, dotprod) can be enabled either from a -march, or from a -mcpu=<cpu> with a cpu that contains that extension -- they are not testing that the extension is enabled from *all* cpus that contain said extension.
Thanks for the updates.
Yeah I agree. It would be useful to add some tests for -mcpu=cortex-a510+crypto and -mcpu=cortex-a510+nocrypto, to make sure they do what is expected.
clang/docs/ReleaseNotes.rst | ||
---|---|---|
77 | Can you add an Arm section below and move this to it. |
Thanks, but did this change miss being updated in the review?
clang/docs/ReleaseNotes.rst | ||
---|---|---|
77 | This still needs doing. Also please add a line to the arm section saying "Added support for the Armv9-A, Armv9.1-A and Armv9.2-A architectures." It looks like there are some llvm release notes in llvm/docs/ReleaseNotes.rst too, that could have a line added. | |
llvm/include/llvm/Support/AArch64TargetParser.def | ||
131 | AEK_PAUTH is twice here. |
Added crypto and no-crypto tests for -mcpu and added new section for Arm and AArch64 support in release notes.
clang/docs/ReleaseNotes.rst | ||
---|---|---|
77 | I didn't add support for these architectures. This may already be in its own commit. |
Thanks for the changes. Nice working pulling this into shape.
LGTM
llvm/include/llvm/Support/AArch64TargetParser.def | ||
---|---|---|
131 | Can you make sure you remove the second PAUTH here before committing. |
clang/docs/ReleaseNotes.rst | ||
---|---|---|
77 | I'll do armv9 in a separate NFC commit |
This seems to be breaking the macOS bot, can you take a look? https://green.lab.llvm.org/green/job/clang-stage1-RA/24735/
Can you add an Arm section below and move this to it.