From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) by sourceware.org (Postfix) with ESMTP id 8B5E4385041C for ; Mon, 17 Aug 2020 18:59:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8B5E4385041C Date: Mon, 17 Aug 2020 19:59:45 +0100 From: Sergei Trofimovich To: Simon Marchi Cc: Tom de Vries , Kevin Buettner , gdb-patches@sourceware.org, Sergei Trofimovich Subject: Re: [PATCH] gdb: fix IA64 build failure of linux-nat Message-ID: <20200817195945.493e921b@sf> In-Reply-To: References: <20200519212710.1417100-1-slyfox@gentoo.org> <20200519150041.13df2b38@f31-4.lan> <20200816094521.061554bb@sf> <5f684182-c8d5-744b-8486-18f89ffb30a3@suse.de> X-Mailer: Claws Mail 3.17.6 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2020 18:59:51 -0000 On Mon, 17 Aug 2020 04:21:40 -0400 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). > > 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. > > 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? > > 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? I'm occasionally using gdb on ia64 for real debugging. I'm part of the team that still keeps ia64 port alive in Gentoo. (And also a part of team that maintains binutils and gdb). Debian also has a functioning ia64 port and are interested to have gdb running. gdb still comes in handy for bug squashing and poking at disassembly. I'd like to tackle a few slightly more substantial bugs on binutils-gdb-ia64 in hopes to prolong ia64's life a bit more (if it's not much of a maintenance burden for other ports). But I don't promise anything :) Basic gdb support still works fine: """ # uname -a Linux guppy 4.19.86-gentoo #4 SMP Fri Dec 6 23:07:34 UTC 2019 ia64 Dual-Core Intel(R) Itanium(R) Processor 9040 GenuineIntel GNU/Linux # gdb ./a GNU gdb (Gentoo 9.2 vanilla) 9.2 ... (gdb) start Temporary breakpoint 1 at 0x7f1 Starting program: /root/a Failed to read a valid object file image from memory. Temporary breakpoint 1, 0x20000008000007f1 in main () (gdb) disassemble Dump of assembler code for function main: 0x20000008000007f0 <+0>: [MII] mov r2=r12 => 0x20000008000007f1 <+1>: mov r14=r0;; 0x20000008000007f2 <+2>: mov r8=r14 0x2000000800000800 <+16>: [MIB] mov r12=r2 0x2000000800000801 <+17>: nop.i 0x0 0x2000000800000802 <+18>: br.ret.sptk.many b0;; End of assembler dump. """ -- Sergei