This is an archive of the discontinued LLVM Phabricator instance.

[libc] Select FPUtils implementations via code instead of build
ClosedPublic

Authored by gchatelet on Dec 3 2021, 2:10 AM.

Details

Summary

We want to simplify the build system and rely on code to do the implementation selection.
This is in preparation of adding a Bazel configuration (D114712).

Diff Detail

Event Timeline

gchatelet created this revision.Dec 3 2021, 2:10 AM
gchatelet requested review of this revision.Dec 3 2021, 2:10 AM
sivachandra accepted this revision.Dec 3 2021, 5:19 AM

Please wait for lntue as he is also planning some refactoring around FMA.h.

libc/src/__support/FPUtil/FEnvImpl.h
15

Nit: Any reason why prefer full paths instead of relative paths?

This revision is now accepted and ready to land.Dec 3 2021, 5:19 AM

Please wait for lntue as he is also planning some refactoring around FMA.h.

Sure!

libc/src/__support/FPUtil/FEnvImpl.h
15

Either is fine, I just aimed for consistency. I can do relative everywhere if you prefer.

lntue accepted this revision.Dec 3 2021, 5:44 AM

You can go ahead with updating FMA.h. I can merge after your submission.

gchatelet updated this revision to Diff 391644.Dec 3 2021, 7:44 AM
  • Use relative path for includes

You can go ahead with updating FMA.h. I can merge after your submission.

SGTM. I've used relative paths for the includes and I'll wait for the builder to go green before submitting.