This is an archive of the discontinued LLVM Phabricator instance.

[RISCV] Implement benchmark::cycleclock::Now for riscv64-linux
ClosedPublic

Authored by rogfer01 on Jul 23 2019, 6:55 AM.

Diff Detail

Repository
rL LLVM

Event Timeline

rogfer01 created this revision.Jul 23 2019, 6:55 AM
Herald added a project: Restricted Project. · View Herald Transcript
lebedev.ri requested changes to this revision.EditedJul 23 2019, 7:41 AM

Thank you for working on this.

This isn't proper solution.
That was recently fixed in https://github.com/google/benchmark/pull/833 by @lenary,
and was cherry-picked to test-suite copy of benchmark in D64237.
Please apply the same diff as in D64237 to llvm/utils/benchmark/ and libcxx/utils/google-benchmark/

This revision now requires changes to proceed.Jul 23 2019, 7:41 AM
rogfer01 updated this revision to Diff 211323.Jul 23 2019, 9:52 AM

ChangeLog:

  • Cherrypick D64237 to other existing copies of cycleclock.h
rogfer01 marked an inline comment as done.Jul 23 2019, 9:54 AM

Thanks a lot for the guidance @lebedev.ri. I wasn't aware of @lenary change and the other copies.

libcxx/utils/google-benchmark/README.LLVM
9 ↗(On Diff #211323)

I couldn't tell exactly on what version this copy is based, hope this wording is fine.

lebedev.ri accepted this revision.Jul 23 2019, 9:59 AM

LG, thank you!

This revision is now accepted and ready to land.Jul 23 2019, 9:59 AM
lenary accepted this revision.Jul 23 2019, 10:09 AM

Looks good. Small nit below, but beyond that all is fine.

libcxx/utils/google-benchmark/README.LLVM
9 ↗(On Diff #211323)

It seems to be based on https://github.com/google/benchmark/commit/4528c76b718acc9b57956f63069c699ae21edcab - might be worth noting this in the readme. (This commit is between v1.4.1 and v1.5.0).

rogfer01 updated this revision to Diff 211413.Jul 23 2019, 10:16 PM

ChangeLog

  • State on top of which commit of libcxx's copy we are cherry-picking.
This revision was automatically updated to reflect the committed changes.
aurel32 added a subscriber: aurel32.Aug 3 2019, 3:10 AM

Disclaimer: I know nothing about LLVM procedures, so please ignore if it is not something acceptable

This commit is one of the only missing to get LLVM 9 building on a RISC-V 64 GNU/Linux system. Therefore would it be possible to backport it to the 9 branch?

lebedev.ri added a subscriber: hans.Aug 3 2019, 3:14 AM

Disclaimer: I know nothing about LLVM procedures, so please ignore if it is not something acceptable

This commit is one of the only missing to get LLVM 9 building on a RISC-V 64 GNU/Linux system. Therefore would it be possible to backport it to the 9 branch?

Best to file an issue and put it as a blocker for https://bugs.llvm.org/show_bug.cgi?id=42474

hans added a comment.Aug 5 2019, 1:13 AM

Disclaimer: I know nothing about LLVM procedures, so please ignore if it is not something acceptable

This commit is one of the only missing to get LLVM 9 building on a RISC-V 64 GNU/Linux system. Therefore would it be possible to backport it to the 9 branch?

Best to file an issue and put it as a blocker for https://bugs.llvm.org/show_bug.cgi?id=42474

I've merged this as r367810 (llvm) and r367813 (libcxx).

I've merged this as r367810 (llvm) and r367813 (libcxx).

Thanks!