Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Ivan Kokshaysky <ink@unseen.parts>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] alpha, ld: remove -taso option
Date: Fri, 17 Jan 2025 14:47:28 +0000	[thread overview]
Message-ID: <87tt9xjy4f.fsf@gentoo.org> (raw)
In-Reply-To: <Z4pr4tVtVYToa5YU@minute> (Ivan Kokshaysky's message of "Fri, 17 Jan 2025 15:40:34 +0100")

Ivan Kokshaysky <ink@unseen.parts> writes:

> The -taso switch was quite useful 25 years ago for porting 32-bit
> code with broken integer-pointer casting. Not anymore. The EF_ALPHA_32BIT
> support is going to be dropped in Linux kernel v6.14 [1], NetBSD and OpenBSD
> never had it, so there is no point in keeping the -taso option around.
>
> Also remove alpha special case that uses -taso from gdb.base/dump.exp
> in gdb testsuite.
>
> [1] https://lore.kernel.org/all/87jzb2tdb7.fsf_-_@email.froward.int.ebiederm.org
>
> Signed-off-by: Ivan Kokshaysky <ink@unseen.parts>
> ---
>  gdb/testsuite/gdb.base/dump.exp |  6 ------
>  ld/emultempl/alphaelf.em        | 31 -------------------------------
>  ld/po/bg.po                     |  7 -------
>  ld/po/es.po                     |  9 ---------
>  ld/po/fi.po                     | 12 ------------
>  ld/po/fr.po                     |  9 ---------
>  ld/po/ka.po                     |  7 -------
>  ld/po/ld.pot                    |  8 --------
>  ld/po/pt_BR.po                  |  9 ---------
>  ld/po/ro.po                     |  9 ---------
>  ld/po/ru.po                     |  9 ---------
>  ld/po/sr.po                     |  9 ---------
>  ld/po/sv.po                     | 12 ------------
>  ld/po/uk.po                     |  9 ---------
>  14 files changed, 146 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.base/dump.exp b/gdb/testsuite/gdb.base/dump.exp
> index 58fedb1d36b..54efe51fbaa 100644
> --- a/gdb/testsuite/gdb.base/dump.exp
> +++ b/gdb/testsuite/gdb.base/dump.exp
> @@ -26,12 +26,6 @@ set endian "auto"
>  
>  set formats {binary ihex srec tekhex  verilog}
>  
> -if {[istarget "alpha*-*-*"]} {
> -    # SREC etc cannot handle 64-bit addresses.  Force the test
> -    # program into the low 31 bits of the address space.
> -    lappend options "ldflags=-Wl,-taso"
> -}

Is this part right? SREC is a debugging format, so if we're going to do
this, we'd need to drop the SREC format, or accept it's going to be
untested, I think?

Adding gdb-patches@.

> [...]

thanks,
sam

       reply	other threads:[~2025-01-17 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Z4pr4tVtVYToa5YU@minute>
2025-01-17 14:47 ` Sam James [this message]
2025-01-17 15:00   ` Ivan Kokshaysky
2025-01-17 21:17     ` Sam James
2025-01-18  7:33 ` Maciej W. Rozycki
2025-01-18  7:37   ` Maciej W. Rozycki
2025-01-18  8:40     ` Ivan Kokshaysky
2025-01-18 10:17     ` [PATCH v2] " Ivan Kokshaysky
2025-01-20 17:50       ` Maciej W. Rozycki
     [not found]       ` <f203eaa7-41a5-4b87-80cc-ab0d0e2edd9c@redhat.com>
2025-02-11 17:02         ` Maciej W. Rozycki
2025-02-11 17:43       ` Andrew Burgess
2025-02-15  1:36         ` Maciej W. Rozycki

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=87tt9xjy4f.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ink@unseen.parts \
    /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