NASP/cuda-samples
35
0
Fork 0
mirror of https://github.com/NVIDIA/cuda-samples.git synced 2024-11-24 19:59:17 +08:00
Code Issues Packages Projects Releases Wiki Activity
e8568c4173
cuda-samples/Samples/0_Introduction/simplePrintf
History
Rob Nertney e8568c4173 Fixing jitlto regression, including missing cuDLA source files for bug #235, and updating changelogs
2023-11-09 16:52:00 +00:00
..
.vscode add and update samples for CUDA 11.6 2022-01-13 11:35:24 +05:30
Makefile Changelog updates 2023-06-29 19:33:40 +00:00
README.md Fixing jitlto regression, including missing cuDLA source files for bug #235, and updating changelogs 2023-11-09 16:52:00 +00:00
simplePrintf_vs2017.sln add and update samples for CUDA 11.6 2022-01-13 11:35:24 +05:30
simplePrintf_vs2017.vcxproj Updating Samples for 12.3 and updating props files 2023-10-23 18:44:49 +00:00
simplePrintf_vs2019.sln add and update samples for CUDA 11.6 2022-01-13 11:35:24 +05:30
simplePrintf_vs2019.vcxproj Updating Samples for 12.3 and updating props files 2023-10-23 18:44:49 +00:00
simplePrintf_vs2022.sln add and update samples for CUDA 11.6 2022-01-13 11:35:24 +05:30
simplePrintf_vs2022.vcxproj Updating Samples for 12.3 and updating props files 2023-10-23 18:44:49 +00:00
simplePrintf.cu add and update samples for CUDA 11.6 2022-01-13 11:35:24 +05:30

README.md

simplePrintf - simplePrintf

Description

This basic CUDA Runtime API sample demonstrates how to use the printf function in the device code.

Key Concepts

Debugging

Supported SM Architectures

SM 5.0 SM 5.2 SM 5.3 SM 6.0 SM 6.1 SM 7.0 SM 7.2 SM 7.5 SM 8.0 SM 8.6 SM 8.7 SM 8.9 SM 9.0

Supported OSes

Linux, Windows

Supported CPU Architecture

x86_64, ppc64le, armv7l

CUDA APIs involved

CUDA Runtime API

cudaGetDeviceProperties, cudaDeviceSynchronize, cudaGetDevice

Prerequisites

Download and install the CUDA Toolkit 12.3 for your corresponding platform.

Build and Run

Windows

The Windows samples are built using the Visual Studio IDE. Solution files (.sln) are provided for each supported version of Visual Studio, using the format:

*_vs<version>.sln - for Visual Studio <version>

Each individual sample has its own set of solution files in its directory:

To build/examine all the samples at once, the complete solution files should be used. To build/examine a single sample, the individual sample solution files should be used.

Note: Some samples require that the Microsoft DirectX SDK (June 2010 or newer) be installed and that the VC++ directory paths are properly set up (Tools > Options...). Check DirectX Dependencies section for details."

Linux

The Linux samples are built using makefiles. To use the makefiles, change the current directory to the sample directory you wish to build, and run make:

$ cd <sample_dir>
$ make

The samples makefiles can take advantage of certain options:

  • TARGET_ARCH= - cross-compile targeting a specific architecture. Allowed architectures are x86_64, ppc64le, armv7l. By default, TARGET_ARCH is set to HOST_ARCH. On a x86_64 machine, not setting TARGET_ARCH is the equivalent of setting TARGET_ARCH=x86_64.
    $ make TARGET_ARCH=x86_64
    $ make TARGET_ARCH=ppc64le
    $ make TARGET_ARCH=armv7l
    See here for more details.

  • dbg=1 - build with debug symbols

    $ make dbg=1

  • SMS="A B ..." - override the SM architectures for which the sample will be built, where "A B ..." is a space-delimited list of SM architectures. For example, to generate SASS for SM 50 and SM 60, use SMS="50 60".

    $ make SMS="50 60"

  • HOST_COMPILER=<host_compiler> - override the default g++ host compiler. See the Linux Installation Guide for a list of supported host compilers.

    $ make HOST_COMPILER=g++

References (for more details)