search for: gpu3

...or instance, the compiler emits references to support routine "foo" as "foo$gpu1". Then you construct the support libraries with aliases for each support function. So a particular implementation of foo in an archive may show up in the symbol table through its aliases "foo$gpu3", "foo$gpu4", "foo$gpu7". When the linker is only looking for "foo$gpu1", it will ignore all other foo implementations and just pick the one aliased to "foo$gpu1". BTW, Apple/Darwin has a similar issue with supporting multiple CPUs. Our solution is...

AMD would like to add new functionality to ranlib (and later ar and nm) and to the bits of LLVM Core that read (and later write) archives. Herewith a terse summary of the change, which we want to improve support of OpenCL for multiple GPUs in a single run-time. Conceptually, a serialized archive is really 2 pieces: a few header members and a set of normal file members. There are no constraints on

...or instance, the compiler emits references to support routine "foo" as "foo$gpu1". Then you construct the support libraries with aliases for each support function. So a particular implementation of foo in an archive may show up in the symbol table through its aliases "foo$gpu3", "foo$gpu4", "foo$gpu7". When the linker is only looking for "foo$gpu1", it will ignore all other foo implementations and just pick the one aliased to "foo$gpu1". I'll have to think about this… We try to treat the IR emitted by the front-end as p...