The linker wrapper is used to perform linking and wrapping of embedded
device object files. Currently its internals are not able to be tested
easily. This patch adds the --dry-run and --print-wrapped-module
options to investigate the link jobs that will be run along with the
wrapped code that will be created to register the binaries.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Looks like this breaks tests on Mac: http://45.33.8.238/macm1/33656/step_7.txt
Please take a look and revert for now if it takes a while to fix. (Maybe just needs an explicit triple?)
Yeah I probably just need to specify the triple, I forgot that Mach-O doesn't like these section names. I pushed rG1dfe0273fda3 to address this, let me know if it's still broken.
clang/test/Driver/linker-wrapper-image.c | ||
---|---|---|
8 | On PowerPC I'm seeing the following error: pointing at @ char: Are you aware of this? | |
clang/test/Driver/linker-wrapper.c | ||
9 | Similar error to above, the coordinates are off by 2 because of subsequent changes: clang/test/Driver/linker-wrapper.c:11:16: error: NVPTX_LINK: expected string not found in input |
clang/test/Driver/linker-wrapper-image.c | ||
---|---|---|
8 | Do you have a link to a buildbot with the full error log? I'll try to test it locally by manually setting the triple. |
clang/test/Driver/linker-wrapper-image.c | ||
---|---|---|
8 | I tested this on a PPC64LE machine and couldn't reproduce, do you have any more information? |
clang/test/Driver/linker-wrapper-image.c | ||
---|---|---|
8 | Yes, those test cases do pass on external bots. At the time of reporting I did not know this affects only the internal builds. We will handle this internally. |
On PowerPC I'm seeing the following error: pointing at @ char:
clang/test/Driver/linker-wrapper-image.c:10:12: error: OPENMP: expected string not found in input
// OPENMP: @__start_omp_offloading_entries = external hidden constant %__tgt_offload_entry
Are you aware of this?