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: Mon, 17 Aug 2020 10:54:42 +0200	[thread overview]
Message-ID: <5f684182-c8d5-744b-8486-18f89ffb30a3@suse.de> (raw)
In-Reply-To: <ef867c85-2f1b-6521-1d61-9e81721c0067@simark.ca>

On 8/16/20 11:51 PM, Simon Marchi wrote:
> On 2020-08-16 4:45 a.m., Sergei Trofimovich via Gdb-patches wrote:
>> On Tue, 19 May 2020 15:00:41 -0700
>> Kevin Buettner <kevinb@redhat.com> wrote:
>>
>>> On Tue, 19 May 2020 22:27:10 +0100
>>> Sergei Trofimovich via Gdb-patches <gdb-patches@sourceware.org> wrote:
>>>
>>>> From: Sergei Trofimovich <siarheit@google.com>
>>>>
>>>> On IA64 built failed as:
>>>>
>>>> ```
>>>> ia64-linux-nat.c:352:29: error: 'gdbarch_num_regs' was not declared in this scope
>>>>   352 |   if (regno < 0 || regno >= gdbarch_num_regs (gdbarch))
>>>>       |                             ^~~~~~~~~~~~~~~~
>>>> ```
>>>>
>>>> The fix includes "gdbarch.h" header where symbol is declared.
>>>>
>>>> 	* gdb/ia64-linux-nat.c: include "gdbarch.h" to declare used
>>>> 	'gdbarch_num_regs'.  
>>>
>>> Okay, but please capitalize "include" in the ChangeLog entry prior
>>> to pushing this change.
>>
>> Attached v2-* patch with capitalization changes.
>>
>> I don't have a 'gdb' write access yet (I think), but I do have GCC one.
>>
>> Should I request 'gdb' access as well as specified in
>>     https://sourceware.org/cgi-bin/pdw/ps_form.cgi ?
> 
> Yes, that would be useful if you plan on contributing regularly.  If it's just
> a occasional patch, we can also push for you.  As you wish.
> 
>>
>> Thank you for the review! 
> 
> A few more styling nits:
> 
>> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
>> index 9cc7e44cba7..8865e6949d6 100644
>> --- a/gdb/ChangeLog
>> +++ b/gdb/ChangeLog
>> @@ -4564,6 +4564,11 @@
>>
>>  	* sparc64-tdep.c (adi_tag_fd): Update call to target_fileio_open.
>>
>> +2020-05-19  Sergei Trofimovich  <siarheit@google.com>
>> +
>> +	* gdb/ia64-linux-nat.c: Include "gdbarch.h" to declare used
>> +	'gdbarch_num_regs'.
> 
> The file path should be relative to the ChangeLog location, so here just "ia64-linux-nat.c".
> 
> Also, make sure that your new entry is at the top of the file (here, it's at line 4564), and
> that you update the date to $TODAY when you push.  For these reasons, most people don't include
> the ChangeLog bits in the patch directly, but just include it in the commit log (as you did).
> Of course, when pushing the patch, then you need to insert it in the ChangeLog file.
> 

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



  reply	other threads:[~2020-08-17  8:54 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 [this message]
2020-08-17  8:21         ` Simon Marchi
2020-08-17 18:59           ` Sergei Trofimovich
2020-08-18  8:46           ` Tom de Vries
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=5f684182-c8d5-744b-8486-18f89ffb30a3@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