[PATCH] D96248: [OpenMP][AMDGPU] Add support for linking libomptarget bitcode
Jon Chesterfield via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Sat Jan 8 11:52:17 PST 2022
JonChesterfield added inline comments.
================
Comment at: clang/include/clang/Driver/Options.td:948
def libomptarget_nvptx_bc_path_EQ : Joined<["--"], "libomptarget-nvptx-bc-path=">, Group<i_Group>,
HelpText<"Path to libomptarget-nvptx bitcode library">;
def dD : Flag<["-"], "dD">, Group<d_Group>, Flags<[CC1Option]>,
----------------
jdoerfert wrote:
> Why do we need two options that literally do the same thing?
> I cannot think of a use case where we would specify two distinct paths, can anyone else?
It's for when someone has decided to put nvptx bitcode in one directory and amdgpu in another. That's presently useless. It might be more helpful once we can target both platforms from one compile, but even then passing bitcode-path once per arch seems better.
In favour of throwing one option away and renaming the other to work on both/all targets
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D96248/new/
https://reviews.llvm.org/D96248
More information about the cfe-commits
mailing list