Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>,
	Sergei Trofimovich <slyfox@gentoo.org>,
	Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, Sergei Trofimovich <siarheit@google.com>
Subject: Re: [PATCH] gdb: fix IA64 build failure of linux-nat
Date: Tue, 18 Aug 2020 10:46:26 +0200	[thread overview]
Message-ID: <84fc876b-1e3c-8342-d342-ec68985cc273@suse.de> (raw)
In-Reply-To: <a060b319-d851-4074-c2f0-2f8d354cb4e0@simark.ca>

On 8/17/20 10:21 AM, Simon Marchi wrote:
> On 2020-08-17 4:54 a.m., Tom de Vries wrote:
>> Hi,
>>
>> IA64 support was just obsoleted in bfd (commit 73d0dc162e "Obsolete ia64").
>>
>> So, AFAIU, this should now be built with --enable-obsolete.
>>
>> What are the consequences for gdb IA64 patches ?
>>
>> Thanks,
>> - Tom
> 
> By transitivity, I'd say that the GDB port is also obsolete.  But as long as it's in
> the tree, it's fine to accept patches to keep it building (otherwise it's useless to
> keep it in the tree).
> 

Btw, I just found in gdb/configure.tgt:
...
    echo "*** Configuration $targ is obsolete." >&2
    echo "*** Support has been REMOVED." >&2
    exit 1
...
So, maybe in gdb a target is obsolete once it's removed?  There seems to
be no separate means to declare a target obsolete before it's removed.

> If you wanted to build GDB with --target=ia64-something-something, you'll need to pass
> --enable-obsolete in order to build BFD, which is a required dependency of GDB.  When we
> pass --enable-targets=all, it builds a GDB with ia64 support without requiring that
> --enable-obsolete flag though.
> 

Hmm, I find that last bit surprising.

> Do you know what's the BFD policy for obsolete configurations?  If they wanted to get
> rid of it completely, they would need to remove GDB support too, otherwise they'd break
> the build.  So should we eventually take the lead and remove support for it first?
> 

I don't know the policy, but the discussion about ia64 took place here (
https://sourceware.org/pipermail/binutils/2020-August/112825.html ,
helpfully titled "Time to obsolete arm-symbian?" ).  It was mentioned
that there was a segfault since at least binutils 2.31 on ia64, which
had not been addressed by anybody, and "Assuming no one cares enough
about ia64 to contribute fixes for the segfaults, ia64 would remain in
binutils until after the next release, at which point the ia64 support
code might be removed".

Thanks,
- Tom

> Sergei, quick survey: do you, or someone you know actually use GDB on ia64?  Or you just
> noticed it not building because you package it?
> 
> Simon
> 


  parent reply	other threads:[~2020-08-18  8:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 21:27 Sergei Trofimovich
2020-05-19 22:00 ` Kevin Buettner
2020-08-16  8:45   ` Sergei Trofimovich
2020-08-16 21:51     ` Simon Marchi
2020-08-17  8:54       ` Tom de Vries
2020-08-17  8:21         ` Simon Marchi
2020-08-17 18:59           ` Sergei Trofimovich
2020-08-18  8:46           ` Tom de Vries [this message]
2020-08-17 20:57       ` Sergei Trofimovich
2020-08-17 21:04         ` Simon Marchi

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=84fc876b-1e3c-8342-d342-ec68985cc273@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=siarheit@google.com \
    --cc=simark@simark.ca \
    --cc=slyfox@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