search for: yourbackend

Hi, is it possible to reduce link time by excluding unused target backends? I would like to type tools/llc make -target=... , and just build it for one backend. /Jonas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110311/c2179915/attachment.html>

...y excluding unused target backends? > > I would like to type > > tools/llc make -target=... , and just build it for one backend. If you build with configure && make, use the configure option --enable-targets. If you build with cmake && make, pass -DLLVM_TARGETS_TO_BUILD=YOURBACKEND to cmake. See http://www.llvm.org/docs/CMake.html for more info on building with cmake.

...expectation of extra work doesn't come for nothing: we expect you to contribute back fixes and improvements that you find, and to work with other community members to coordinate projects as appropriate. When looking at a new backend, I should expect to see few-to-no diffs outside of lib/Target/YourBackend, and a few other places (Triple.cpp, for example). All other changes should already be upstreamed. > > * Test plan - If you're going to expect us to maintain and fix your code, then you need to have a good answer to how to test it. This includes, but is not limited to, a good set of re...

...work doesn't come for nothing: we > expect you to contribute back fixes and improvements that you find, and > to work with other community members to coordinate projects as > appropriate. When looking at a new backend, I should expect to see few- > to-no diffs outside of lib/Target/YourBackend, and a few other places > (Triple.cpp, for example). All other changes should already be > upstreamed. > > > > * Test plan - If you're going to expect us to maintain and fix your > code, then you need to have a good answer to how to test it. This > includes, but is not...

...expectation of extra work doesn't come for nothing: we expect you to contribute back fixes and improvements that you find, and to work with other community members to coordinate projects as appropriate. When looking at a new backend, I should expect to see few-to-no diffs outside of lib/Target/YourBackend, and a few other places (Triple.cpp, for example). All other changes should already be upstreamed. * Test plan - If you're going to expect us to maintain and fix your code, then you need to have a good answer to how to test it. This includes, but is not limited to, a good set of regression t...