From: Lancelot SIX <Lancelot.Six@amd.com>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.rocm: Don't include unistd.h when not necessary
Date: Fri, 3 Jul 2026 11:49:36 +0100 [thread overview]
Message-ID: <02483ec7-713d-472f-a5e8-0e49e4b85dc5@amd.com> (raw)
In-Reply-To: <20260702122325.330129-1-pedro@palves.net>
On 02/07/2026 13:23, Pedro Alves wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> gdb.rocm/code-object-load-while-breakpoint-hit.cpp is including
> unistd.h unnecessarily AFAICS. Don't include it, so this test can
> compile on Windows (x86_64-pc-windows-msvc) as well.
>
> Change-Id: I9f469fd4b061ab9895c8bbbd408939e4df2a4e92
Good catch, this looks good to me.
Approve-by: Lancelot Six <lancelot.six@amd.com> (amdgpu)
Best,
Lancelot.
> ---
> gdb/testsuite/gdb.rocm/code-object-load-while-breakpoint-hit.cpp | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/gdb/testsuite/gdb.rocm/code-object-load-while-breakpoint-hit.cpp b/gdb/testsuite/gdb.rocm/code-object-load-while-breakpoint-hit.cpp
> index d2f2ddcbf6c..d7101b419c0 100644
> --- a/gdb/testsuite/gdb.rocm/code-object-load-while-breakpoint-hit.cpp
> +++ b/gdb/testsuite/gdb.rocm/code-object-load-while-breakpoint-hit.cpp
> @@ -36,7 +36,6 @@ kernel ()
> #else
>
> #include <hip/hip_runtime.h>
> -#include <unistd.h>
>
> #include "rocm-test-utils.h"
>
>
> base-commit: 18ca02157d9cc245f035452e397a07a3787034d0
> --
> 2.54.0
>
prev parent reply other threads:[~2026-07-03 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:23 Pedro Alves
2026-07-03 10:49 ` Lancelot SIX [this message]
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=02483ec7-713d-472f-a5e8-0e49e4b85dc5@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--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