From: Lancelot SIX <Lancelot.Six@amd.com>
To: gdb-patches@sourceware.org
Cc: lsix@lancelotsix.com, Pedro Alves <pedro@palves.net>
Subject: Re: [PATCH 4/4] gdb/testsuite: allow_hipcc_tests tests the hipcc compiler
Date: Tue, 7 Feb 2023 13:42:03 +0000 [thread overview]
Message-ID: <ffe57bdb-3d15-9044-d100-a9dac5f690e2@amd.com> (raw)
In-Reply-To: <20230207132802.223510-5-lancelot.six@amd.com>
Hi,
Some of this patch is based on original work from Pedro in
https://github.com/ROCm-Developer-Tools/ROCgdb/commit/031a44b9c6ec2c381030a919b837e5dfc255e688.
I just realized that I forgot to give credit where due.
I'll add the following tag:
Co-Authored-By: Pedro Alves <pedro@palves.net>
Best,
Laneclot.
On 07/02/2023 13:28, Lancelot SIX wrote:
> Update allow_hipcc_tests so all gdb.rocm tests are skipped if we do not
> have a working hipcc compiler available.
>
> To achieve this, adjust gdb_simple_compile to ensure that the hip
> program is saved in a ".cpp" file before calling hipcc otherwise
> compilation will fail.
>
> One thing to note is that it is possible to have a hipcc installed with
> a CUDA backend. Compiling with this back-end will successfully result
> in an application, but GDB cannot debug it (at least for the offload
> part). In the context of the gdb.rocm tests, we want to detect such
> situation where gdb_simple_compile would give a false positive.
>
> To achieve this, this patch checks that there is at least one AMDGPU
> device available and that hipcc can compile for this or those targets.
> Detecting the device is done using the rocm_agent_enumerator tool which
> is installed with the all ROCm installations (it is used by hipcc to
> detect identify targets if this is not specified on the comand line).
>
> This patch also makes the allow_hipcc_tests proc a cached proc.
> ---
> gdb/testsuite/lib/gdb.exp | 4 +++
> gdb/testsuite/lib/rocm.exp | 69 +++++++++++++++++++++++++++++++++++++-
> 2 files changed, 72 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index faa0ac05a9a..6333728f71e 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -4581,6 +4581,10 @@ proc gdb_simple_compile {name code {type object} {compile_flags {}} {object obj}
> set ext "go"
> break
> }
> + if { "$flag" eq "hip" } {
> + set ext "cpp"
> + break
> + }
> }
> set src [standard_temp_file $name-[pid].$ext]
> set obj [standard_temp_file $name-[pid].$postfix]
> diff --git a/gdb/testsuite/lib/rocm.exp b/gdb/testsuite/lib/rocm.exp
> index b5b59748c27..06d5b3988b8 100644
> --- a/gdb/testsuite/lib/rocm.exp
> +++ b/gdb/testsuite/lib/rocm.exp
> @@ -15,7 +15,51 @@
> #
> # Support library for testing ROCm (AMD GPU) GDB features.
>
> -proc allow_hipcc_tests { } {
> +# Get the list of gpu targets to compile for.
> +#
> +# If HCC_AMDGPU_TARGET is set in the environment, use it. Otherwise,
> +# try reading it from the system using the rocm_agent_enumerator
> +# utility.
> +
> +proc hcc_amdgpu_targets {} {
> + # Look for HCC_AMDGPU_TARGET (same env var hipcc uses). If
> + # that fails, try using rocm_agent_enumerator (again, same as
> + # hipcc does).
> + if {[info exists ::env(HCC_AMDGPU_TARGET)]} {
> + return [split $::env(HCC_AMDGPU_TARGET) ","]
> + }
> +
> + set rocm_agent_enumerator "rocm_agent_enumerator"
> +
> + # If available, use ROCM_PATH to locate rocm_agent_enumerator.
> + if { [info exists ::env(ROCM_PATH)] } {
> + set rocm_agent_enumerator \
> + "$::env(ROCM_PATH)/bin/rocm_agent_enumerator"
> + }
> +
> + # If we fail to locate the rocm_agent_enumerator, just return an empty
> + # list of targets and let the caller decide if this should be an error.
> + if { [which $rocm_agent_enumerator] == 0 } {
> + return [list]
> + }
> +
> + set result [remote_exec host $rocm_agent_enumerator]
> + if { [lindex $result 0] != 0 } {
> + error "rocm_agent_enumerator failed"
> + }
> +
> + set targets [list]
> + foreach target [lindex $result 1] {
> + # Ignore gfx000 which is the host CPU.
> + if { $target ne "gfx000" } {
> + lappend targets $target
> + }
> + }
> +
> + return $targets
> +}
> +
> +gdb_caching_proc allow_hipcc_tests {
> # Only the native target supports ROCm debugging. E.g., when
> # testing against GDBserver, there's no point in running the ROCm
> # tests.
> @@ -29,6 +73,29 @@ proc allow_hipcc_tests { } {
> return 0
> }
>
> + # Check we have a working hipcc compiler available.
> + set targets [hcc_amdgpu_targets]
> + if { [llength $targets] == 0} {
> + return 0
> + }
> +
> + set flags [list hip additional_flags=--offload-arch=[join $targets ","]]
> + if {![gdb_simple_compile hipprobe {
> + #include <hip/hip_runtime.h>
> + __global__ void
> + kern () {}
> +
> + int
> + main ()
> + {
> + kern<<<1, 1>>> ();
> + hipDeviceSynchronize ();
> + return 0;
> + }
> + } executable $flags]} {
> + return 0
> + }
> +
> return 1
> }
>
next prev parent reply other threads:[~2023-02-07 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 13:27 [PATCH 0/4] Fix gdb.rocm/simple.exp on hosts without ROCm Lancelot SIX
2023-02-07 13:27 ` [PATCH 1/4] gdb: 'show config' shows --with[out]-amd-dbgapi Lancelot SIX
2023-02-07 13:28 ` [PATCH 2/4] gdb/testsuite: Rename skip_hipcc_tests to allow_hipcc_tests Lancelot SIX
2023-02-07 13:28 ` [PATCH 3/4] gdb/testsuite: require amd-dbgapi support to run rocm tests Lancelot SIX
2023-02-07 13:59 ` Simon Marchi
2023-02-07 13:28 ` [PATCH 4/4] gdb/testsuite: allow_hipcc_tests tests the hipcc compiler Lancelot SIX
2023-02-07 13:42 ` Lancelot SIX [this message]
2023-02-07 14:12 ` Simon Marchi
2023-02-07 15:31 ` Lancelot SIX
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ffe57bdb-3d15-9044-d100-a9dac5f690e2@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=pedro@palves.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).