wuzish added a comment.
> That (controlling within the headers) sounds good to me. When that lands,
> then my understanding is that the `PPCLinuxToolChain` code would be adjusted
> to include `ppc_wrappers` in the search path in the general case. Please let
> me know if that's not the case. Tha
hubert.reinterpretcast added a comment.
> I think the name `ppc_wrappers` is accurate to describe its meaning that
> wrapping the headers under standard library path or standard header search
> path.
Thanks for clarifying this for me. In the case where all of the headers are
expected to be pre
wuzish added inline comments.
/cfe/trunk/lib/Driver/ToolChains/PPCLinux.cpp:26 @hubert.reinterpretcast
Thanks for your advice. I think the name `ppc_wrappers` is accurate to describe
its meaning that wrapping the headers under standard library path or standard
header search path. (Headers in li
hubert.reinterpretcast added inline comments.
/cfe/trunk/lib/Driver/ToolChains/PPCLinux.cpp:26 I'm not particularly concerned
about the scoping of the work; however, the `ppc_wrappers` directory is not at
all indicative of that scoping. It neither indicates the scope in terms of
purpose (provid
jsji added inline comments.
/cfe/trunk/lib/Driver/ToolChains/PPCLinux.cpp:26 yes, it is currently Linux
only. I think we can extend it to include other OS like AIX later if needed.
https://reviews.llvm.org/rL358949
___
cfe-commits mailing list
cfe-
hubert.reinterpretcast added a subscriber: cfe-commits.
https://reviews.llvm.org/rL358949
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
