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

On Fri, Jan 17, 2025 at 02:47:28PM +0000, Sam James wrote:
> Ivan Kokshaysky <ink@unseen.parts> writes:
...
> > 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?

Yes, this test will be skipped just like on any other 64-bit architecture.
But if we keep it, it would fail with linux kernels starting from v6.14.

> Adding gdb-patches@.
> 
> > [...]
> 
> thanks,
> sam

Ivan.

  reply	other threads:[~2025-01-17 15:01 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
2025-01-17 15:00   ` Ivan Kokshaysky [this message]
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=Z4pwoL6nLdW0l611@minute \
    --to=ink@unseen.parts \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sam@gentoo.org \
    /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