From: Luis Machado <luis.machado@arm.com>
To: Pedro Alves <pedro@palves.net>,
Andrew Burgess <aburgess@redhat.com>,
John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] gdb: native target invalid architecture detection
Date: Wed, 8 Jun 2022 09:18:50 +0100 [thread overview]
Message-ID: <49bdabab-414e-85c7-4fd3-bec68ac9822a@arm.com> (raw)
In-Reply-To: <fb9a98e7-2013-b347-3cd7-c54b12617746@palves.net>
On 6/7/22 21:15, Pedro Alves wrote:
> On 2022-06-07 19:42, Pedro Alves wrote:
>
>> When we use gcc for arm-linux target, its file name can be different,
>> arm-linux-gnueabihf-gcc, arm-linux-gnueabi-gcc, or arm-none-linux-gnueabi-gcc,
>> so I add a variable ARM_CC_FOR_TARGET, so that user can set the name
>> of gcc for arm-linux target on aarch64, like:
>
> ...
>
>> Maybe it would be possible to come up with a way to default ARM_CC_FOR_TARGET to
>> something that works for most people when testing aarch64, somehow.
>
> Maybe something like this? Completely untested, other than hacking it such that
> the aarch64 linux path is taken on my x86-64 box, to ensure the tcl at least parses
> as expected.
>
Thanks for the patch. I think it is fine to have some of these tests run conditionally
based on the presence of an environment variable. What we're really missing is proper
documentation of ARM_CC_FOR_TARGET, explaining what it does, when it should be enabled
and under what conditions.
I wonder if putting that on the GDB manual, under a testing section, would work. The Wiki
has an entry for testing, but I find it a bit chaotic. What do you say?
> I left arm-linux-gnueabihf-gcc last on the theory that binaries produced by
> arm-linux-gnueabi-gcc and arm-none-linux-gnueabi-gcc would run everywhere, but
> arm-linux-gnueabihf-gcc might now. I am not really sure about that, I may be
> making that up.
>
> gdb.multi/multi-arch-exec.exp also uses ARM_CC_FOR_TARGET. If something like
> this works, then we could do the same to that testcase. Even better if we
> manage to factor this out to a shared procedure used by both testcases.
>
> From 56cdd32a54b236d35c433809fcb015f20487dc4b Mon Sep 17 00:00:00 2001
> From: Pedro Alves <pedro@palves.net>
> Date: Tue, 7 Jun 2022 20:11:32 +0100
> Subject: [PATCH] aarch64: gdb.multi/multi-arch.exp: Add fallback if
> ARM_CC_FOR_TARGET not set
>
> On Aarch64, you can set ARM_CC_FOR_TARGET to the 32-bit compiler to
> use when testing gdb.multi/multi-arch.exp. If you set it, then the
> testcase doesn't run.
>
> I guess that approximately nobody remembers to set ARM_CC_FOR_TARGET.
>
> This commit adds a fallback. If ARM_CC_FOR_TARGET is not set, and
> testing for Linux, try arm-linux-gnueabi-gcc,
> arm-none-linux-gnueabi-gcc, arm-linux-gnueabihf-gcc.
>
> Change-Id: Iefe5865d5fc84b4032eaff7f4c5c61582bf75c39
> ---
> gdb/testsuite/gdb.multi/multi-arch.exp | 39 ++++++++++++++++++++++----
> 1 file changed, 34 insertions(+), 5 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.multi/multi-arch.exp b/gdb/testsuite/gdb.multi/multi-arch.exp
> index e5c2d9cc161..a9d442d89ad 100644
> --- a/gdb/testsuite/gdb.multi/multi-arch.exp
> +++ b/gdb/testsuite/gdb.multi/multi-arch.exp
> @@ -61,18 +61,47 @@ set options [list debug]
>
> if [istarget "aarch64*-*-*"] {
> if {[info exists ARM_CC_FOR_TARGET]} {
> - lappend options "compiler=${ARM_CC_FOR_TARGET}"
> + set compilers [list ${ARM_CC_FOR_TARGET}]
> + } elseif [istarget "*-linux*-*"] {
> + # Try a few common compiler names.
> + set compilers {
> + arm-linux-gnueabi-gcc
> + arm-none-linux-gnueabi-gcc
> + arm-linux-gnueabihf-gcc
> + }
> } else {
> + set compilers {}
> + }
> +
> + set ok 0
> + foreach compiler $compilers {
> + set arm_options $options
> + lappend arm_options "compiler=$compiler"
> +
> + if {![is_remote host] && [which $compiler] == 0} {
> + # Avoid "default_target_compile: Can't find
> + # $compiler." warning issued from gdb_compile.
> + continue
> + }
> +
> + if { [gdb_compile "${srcdir}/${subdir}/${srcfile2}" ${exec2} \
> + executable $arm_options] == "" } {
> + set ok 1
> + break
> + }
> + }
> +
> + if {!$ok} {
> unsupported "ARM compiler is not known"
> return -1
> }
> } else {
> lappend options "additional_flags=${march2}"
> -}
>
> -if { [build_executable "failed to prepare" ${exec2} "${srcfile2}" \
> - $options]} {
> - return -1
> + if { [build_executable "failed to prepare" ${exec2} "${srcfile2}" \
> + $options]} {
> + return -1
> + }
> }
>
> # Start inferior 1
>
> base-commit: 0c8cd1de90b97f12b27b40c2922a03a68932eea1
next prev parent reply other threads:[~2022-06-08 8:19 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 14:30 [PATCH 0/5] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-05-31 14:30 ` [PATCH 1/5] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-01 7:58 ` Luis Machado
2022-05-31 14:30 ` [PATCH 2/5] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-05-31 14:30 ` [PATCH 3/5] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-01 8:01 ` Luis Machado
2022-05-31 14:30 ` [PATCH 4/5] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-05-31 16:04 ` John Baldwin
2022-05-31 17:22 ` Andrew Burgess
2022-05-31 14:30 ` [PATCH 5/5] gdb: native target invalid architecture detection Andrew Burgess
2022-05-31 16:08 ` John Baldwin
2022-05-31 16:51 ` Andrew Burgess
2022-06-01 8:25 ` Luis Machado
2022-06-01 21:06 ` John Baldwin
2022-06-01 21:21 ` Christophe Lyon
2022-06-02 14:56 ` John Baldwin
2022-06-06 14:38 ` Andrew Burgess
2022-06-06 17:48 ` Andrew Burgess
2022-06-07 11:03 ` Luis Machado
2022-06-07 18:42 ` Pedro Alves
2022-06-07 20:15 ` Pedro Alves
2022-06-08 8:18 ` Luis Machado [this message]
2022-06-08 10:17 ` Pedro Alves
2022-06-08 7:54 ` Luis Machado
2022-06-08 10:12 ` Pedro Alves
2022-06-08 11:20 ` [PATCH v2] aarch64: Add fallback if ARM_CC_FOR_TARGET not set (was: Re: [PATCH 5/5] gdb: native target invalid architecture detection) Pedro Alves
2022-06-08 12:50 ` Luis Machado
2022-06-08 13:23 ` Pedro Alves
2022-06-08 13:38 ` Andrew Burgess
2022-06-08 19:01 ` John Baldwin
2022-06-08 21:48 ` Pedro Alves
2022-06-09 16:31 ` John Baldwin
2022-06-10 13:08 ` [PATCHv2 0/6] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 1/6] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 2/6] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 3/6] gdb/arm: avoid undefined behaviour in arm_frame_is_thumb Andrew Burgess
2022-06-10 15:21 ` Luis Machado
2022-06-10 15:49 ` Andrew Burgess
2022-06-10 16:29 ` Luis Machado
2022-06-10 13:08 ` [PATCHv2 4/6] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-10 16:35 ` Luis Machado
2022-06-10 13:08 ` [PATCHv2 5/6] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 6/6] gdb: native target invalid architecture detection Andrew Burgess
2022-06-10 16:20 ` John Baldwin
2022-06-10 16:31 ` Luis Machado
2022-06-13 16:15 ` [PATCHv3 0/6] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 1/6] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 2/6] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 3/6] gdb: select suitable thread for gdbarch_adjust_breakpoint_address Andrew Burgess
2022-06-14 9:45 ` Luis Machado
2022-06-14 14:05 ` Andrew Burgess
2022-06-24 16:58 ` Pedro Alves
2022-06-13 16:15 ` [PATCHv3 4/6] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 5/6] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-06-24 18:15 ` Pedro Alves
2022-06-13 16:15 ` [PATCHv3 6/6] gdb: native target invalid architecture detection Andrew Burgess
2022-06-24 19:23 ` Pedro Alves
2022-06-27 16:27 ` Andrew Burgess
2022-06-27 21:38 ` Pedro Alves
2022-06-28 10:37 ` Andrew Burgess
2022-06-28 12:42 ` [PATCH v2] gdb+gdbserver/Linux: avoid reading registers while going through shell (was: Re: [PATCHv3 6/6] gdb: native target invalid architecture detection) Pedro Alves
2022-06-28 14:21 ` Andrew Burgess
2022-06-29 15:17 ` Simon Marchi
2022-06-29 16:22 ` [PATCH] Fix GDBserver regression due to change to avoid reading shell registers Pedro Alves
2022-06-29 16:38 ` Simon Marchi
2022-06-30 9:33 ` [PATCHv3 6/6] gdb: native target invalid architecture detection Andrew Burgess
2022-06-30 11:44 ` Pedro Alves
2022-07-11 10:47 ` Andrew Burgess
2022-06-24 10:15 ` [PATCHv3 0/6] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 0/6] Detect invalid casts of gdbarch_tdep structures Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 1/6] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 2/6] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 3/6] gdb: select suitable thread for gdbarch_adjust_breakpoint_address Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 4/6] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 5/6] gdbsupport: add checked_static_cast Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 6/6] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-07-11 10:46 ` [PATCHv4 0/6] Detect invalid casts of gdbarch_tdep structures Andrew Burgess
2022-07-21 18:21 ` Andrew Burgess
2022-07-22 0:50 ` Luis Machado
2022-07-23 0:02 ` [PATCH] Rename gdbarch_tdep template function to gdbarch_tdep_cast for g++ 4.8 Mark Wielaard
2022-07-25 11:19 ` Andrew Burgess
2022-07-25 11:27 ` Mark Wielaard
2022-07-26 11:05 ` Andrew Burgess
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=49bdabab-414e-85c7-4fd3-bec68ac9822a@arm.com \
--to=luis.machado@arm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).