Project

General

Profile

Bug #881

Automatically determine location of nvcc when compiling programs using charmc in accel

Added by Michael Robson over 3 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Category:
GPU Support
Target version:
-
Start date:
11/09/2015
Due date:
% Done:

0%


Description

When compiling programs that take advantage of the accel framework charmc implicitly invokes nvcc to compile generated cuda code. However, the location of nvcc is hardcoded to /usr/local/cuda/bin instead of whatever is detected when charm is built. Therefore this is related to those issues as well.

There is also nastiness here about checking CMK_CUDA, creating new flags is a separate issue. Ultimately this fix should go in the final accel commit.

Potentially related fix for gpu manager: #511


Related issues

Related to Charm++ - Bug #756: CUDA build does not correctly find cuda location New 05/29/2015
Related to Charm++ - Bug #788: Out of tree build broken for CUDA Merged 07/09/2015
Related to Charm++ - Feature #812: Merge Accel Branch In Progress 08/17/2015
Related to Charm++ - Feature #801: Create separate builds for accel and gpu manager New 08/10/2015

History

#1 Updated by Phil Miller about 3 years ago

  • Category set to Build & Test Automation

#2 Updated by Michael Robson over 2 years ago

  • Target version changed from 6.8.0 to 6.8.1

#3 Updated by Sam White almost 2 years ago

Is this critical for 6.8.1? Retarget to 6.9.0 if not

#4 Updated by Michael Robson almost 2 years ago

  • Target version changed from 6.8.1 to 6.9.0
  • Category changed from Build & Test Automation to GPU Support

Sam White wrote:

Is this critical for 6.8.1? Retarget to 6.9.0 if not

After looking at the title of this bug I realized it was for accel which isn't even integrated yet... It should be (in some form) in 6.9.0 so I'll target it there.

#5 Updated by Michael Robson almost 2 years ago

  • Target version deleted (6.9.0)

Also available in: Atom PDF