是否可以使用 autoconf 检查 nvcc 编译？

发布于 2024-08-16 10:07:23 字数 310 浏览 7 评论 0原文

我正在尝试在配置过程中测试一些典型的cuda功能。我怎样才能把它写在我的configure.ac中？类似于：

AC_TRY_COMPILE([],
[
__global__ static void test_cuda() {
    const int tid = threadIdx.x;
    const int bid = blockIdx.x;
    __syncthreads();
}
],
[cuda_comp=ok],[cuda_comp=no])

但是AC_LANG中没有定义nvcc。我必须创建自己的 m4 宏吗？

原文

I am trying to test some typical cuda functions during the configure process. How can I write it in my configure.ac? Something like:

AC_TRY_COMPILE([],
[
__global__ static void test_cuda() {
    const int tid = threadIdx.x;
    const int bid = blockIdx.x;
    __syncthreads();
}
],
[cuda_comp=ok],[cuda_comp=no])

But nvcc is not defined in AC_LANG. Must I create my own m4 macros?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

故乡的云 2024-08-23 10:07:23

我非常怀疑是否可以干净地挂钩 AC_LANG、AC_TRY_COMPILE 等系列宏而不实际重写 autoconf 的部分内容。

对您来说，安全的选择是只编写一个测试。除非您需要在多个项目中进行该测试，否则您甚至不需要将测试包装在 m4 宏中。

该测试将首先检查 nvcc，然后创建一些测试源文件，最后尝试使用 $NVCC 进行编译。然后它需要检查编译结果（返回代码和生成的文件），最后清理它可能生成的任何文件。

类似的东西

AC_ARG_VAR([NVCC], [nvcc compiler to use])
AC_PATH_PROG([NVCC], [nvcc], [no])
working_nvcc=no
if test "x$NVCC" != "xno"
the
    AC_MSG_CHECKING([whether nvcc works])
    cat>conftest.c<<EOF
    __global__ whatever() {
       ...
    }
EOF
    if $NVCC conftest.c && test_whether_output_files_are_ok
    then
        working_nvcc=yes
    fi
    rm -f conftest.c conftest.o conftest.what conftest.ever
    AC_MSG_RESULT([$working_nvcc])
fi
AM_CONDITIONAL([WORKING_NVCC], [test "x$working_nvcc" = "xyes"])

I am highly doubtful whether it is possible to cleanly hook into the AC_LANG, AC_TRY_COMPILE etc. series of macros without actually rewriting parts of autoconf.

The safe bet for you is to just write a test. Unless you need that test in several projects, you do not even need to wrap the test in m4 macros.

The test would first check for nvcc, then create some test source file and finally try compiling that using $NVCC. Then it needs to examine the results of the compilation (return code and generated files), and finally to clean up any files it might have generated.

Something like

AC_ARG_VAR([NVCC], [nvcc compiler to use])
AC_PATH_PROG([NVCC], [nvcc], [no])
working_nvcc=no
if test "x$NVCC" != "xno"
the
    AC_MSG_CHECKING([whether nvcc works])
    cat>conftest.c<<EOF
    __global__ whatever() {
       ...
    }
EOF
    if $NVCC conftest.c && test_whether_output_files_are_ok
    then
        working_nvcc=yes
    fi
    rm -f conftest.c conftest.o conftest.what conftest.ever
    AC_MSG_RESULT([$working_nvcc])
fi
AM_CONDITIONAL([WORKING_NVCC], [test "x$working_nvcc" = "xyes"])

回复收藏 0 原文

~没有更多了~