This makes it possible to print the name of compiler-rt libraries
by using simply clang -print-file-name=libclang_rt.${runtime}-${arch}.so
same as other libraries, without having to know the details of the
resource directory organization.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
cfe/trunk/include/clang/Driver/ToolChain.h | ||
---|---|---|
312 | By introducing a second way of getting the path to compiler-rt, this created inconsistencies where some platforms that implement getCompilerRT(...) now won't return the right value for getCompilerRTPath(). Is this the intent: getCompilerRT() == append(getCompilerRTPath(), basename(getCompilerRT(...))? If so, I think it would make sense to refactor this a bit so that we have: getCompilerRTDir(); // What's currently called getCompilerRTPath(). This would be overriden by toolchains. getCompilerRTBasename(args...); // Exists currently, but we would override this in the toolchains instead of having a default implementation. getCompilerRT(args...); // This would basically do append(getCompilerRTDir(), getCompilerRTBasename(args...)) WDYT? |
By introducing a second way of getting the path to compiler-rt, this created inconsistencies where some platforms that implement getCompilerRT(...) now won't return the right value for getCompilerRTPath().
Is this the intent: getCompilerRT() == append(getCompilerRTPath(), basename(getCompilerRT(...))? If so, I think it would make sense to refactor this a bit so that we have:
WDYT?