lijiansong added inline comments.
Herald added a subscriber: guansong.
Comment at: lib/Driver/Driver.cpp:2113-2124
+// the resulting list. Otherwise, just append the device actions.
+if (CanUseBundler && !OffloadAL.empty()) {
+ // Add the host action to the list in order to create the bundling
action.
+ OffloadAL.push_back(HostAction);
+
+ // We expect that the host action was just appended to the action list
+ // before this method was called.
hello,
if I want to compile device-only device code, e.g. clang foo.mlu a.cpp -o bar,
I want to get the following action graph:
for foo.mlu:
input -> preprocess->compile->backend->assemble ,
Then i will get foo.o,
for a.cpp:
input -> preprocess->compile->backend->assemble
then I will get a.o
i want to link foo.o with a.o to get bar, a.cpp is the main, while foo.mlu has
the device computation logic.
How can I manage it with offload?
https://reviews.llvm.org/D21852
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
