@@ -3630,10 +3631,17 @@ SDValue SITargetLowering::LowerCall(CallLoweringInfo
,
std::vector Ops;
Ops.push_back(Chain);
+ bool AddTargetGlobalAddr = true;
+ // Try to find the callee in the current module.
+ if (isa(Callee)) {
+Callee =
@@ -937,27 +938,105 @@ bool CodeGenAction::loadLinkModules(CompilerInstance
) {
for (const CodeGenOptions::BitcodeFileToLink :
CI.getCodeGenOpts().LinkBitcodeFiles) {
-auto BCBuf = CI.getFileManager().getBufferForFile(F.Filename);
-if (!BCBuf) {
+
+auto
@@ -937,27 +938,105 @@ bool CodeGenAction::loadLinkModules(CompilerInstance
) {
for (const CodeGenOptions::BitcodeFileToLink :
CI.getCodeGenOpts().LinkBitcodeFiles) {
-auto BCBuf = CI.getFileManager().getBufferForFile(F.Filename);
-if (!BCBuf) {
+
+auto
jhuber6 wrote:
> Would it be feasible to consider switching to the new offloading driver mode
> and really link with the library instead? It may be a conveniently isolated
> use case with little/no existing users that would disrupt.
I've thought a reasonable amount about a `compiler-rt` for
@@ -937,27 +938,105 @@ bool CodeGenAction::loadLinkModules(CompilerInstance
) {
for (const CodeGenOptions::BitcodeFileToLink :
CI.getCodeGenOpts().LinkBitcodeFiles) {
-auto BCBuf = CI.getFileManager().getBufferForFile(F.Filename);
-if (!BCBuf) {
+
+auto
