This can be used to select particular ELF with -xelf option later. All other options are ignored with this flag. Works with host executable/object/library and external fatbin. List all the ELF files available in the fatbin. Print this help information on this tool. Specify GPU Architecture for which information should be dumped. Specify symbol table index of the function whose fat binary structures must be dumped. Specify names of device functions whose fat binary structures must be dumped. All ‘dump’ and ‘list’ options are ignored with this option. To get the list of text binary encoding use -ltext option. All dump and list options are ignored with this option.Įxtract text binary encoding file(s) name containing and save as file(s). To get the list of PTX files use -lptx option. All dump and list options are ignored with this option.Įxtract PTX file(s) name containing and save as file(s).
To get the list of ELF files use -lelf option. Useful in getting all the resource usage information at one place.Įxtract ELF file(s) name containing and save as file(s). By default will only dump contents of executable fatbin (if exists), else relocatable fatbin if no executable fatbin.ĭump PTX for all listed device functions.ĭump CUDA assembly for a single cubin file or all cubin files embedded in the binary.ĭump resource usage for each ELF. cuobjdump Command-line Options ĭump all fatbin sections. Each option has a long name and a short name, which can be used interchangeably. Table 2 contains supported command-line options of cuobjdump, along with a description of what each option does. Note that value for REG, TEXTURE, SURFACE and SAMPLER denotes the count and for other resources it denotes no.
REG:42 STACK:0 SHARED:0 LOCAL:0 CONSTANT:472 TEXTURE:4 SURFACE:0 SAMPLER:1 REG:38 STACK:8 SHARED:4 LOCAL:0 CONSTANT:532 TEXTURE:8 SURFACE:7 SAMPLER:0 REG:24 STACK:8 SHARED:0 LOCAL:0 CONSTANT:472 CONSTANT:24 TEXTURE:0 SURFACE:0 SAMPLER:0 headerflags EF_CUDA_PTX_SM(EF_CUDA_SM70)" Examples of each of these option types are, respectively: Single value options must be specified at most once and list options may be repeated. The tools mentioned above recognize three types of command options: boolean options, single value options and list options.īoolean options do not have an argument, they are either specified on a command line or not. Long options are intended for use in build scripts, where size of the option is less important than descriptive value and short options are intended for interactive use. For example, -I is the short name of -include-path. long names must be preceded by two hyphens and short names must be preceded by a single hyphen. These two variants are distinguished by the number of hyphens that must precede the option name, i.e. This section of the document provides common details about the command line options for the following tools:Įach command-line option has a long name and a short name, which are interchangeable with each other. Comparison of cuobjdump and nvdisasm Įxtract ptx and extract and disassemble cubin from the following input files: Here’s a quick comparison of the two tools: Table 1. Basically, cuobjdump accepts both cubin files and host binaries while nvdisasm only accepts cubin files but nvdisasm provides richer output options. Differences between cuobjdump and nvdisasm ĬUDA provides two binary utilities for examining and disassembling cubin files and host executables: cuobjdump and nvdisasm.
Hopper disassembler read memory driver#
For more details on cubin files or the CUDA compilation trajectory, refer to NVIDIA CUDA Compiler Driver NVCC.
0 kommentar(er)
