Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: will schmidt via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>,
	Luis Machado <luis.machado@linaro.org>,
	Simon Marchi <simon.marchi@efficios.com>,
	gdb-patches@sourceware.org, John Baldwin <jhb@FreeBSD.org>
Subject: Re: [PATCH] gdb: fix gdbarch_tdep ODR violation
Date: Mon, 15 Nov 2021 14:42:43 -0600	[thread overview]
Message-ID: <6f000cddd5fa3bb69f7321667a3aab83225531e9.camel@vnet.ibm.com> (raw)
In-Reply-To: <f2208278-7f0e-74db-71c3-c57fd6a750f9@simark.ca>

On Mon, 2021-11-15 at 11:29 -0500, Simon Marchi wrote:
> On 2021-11-15 5:45 a.m., Luis Machado via Gdb-patches wrote:
> > LGTM
> 
> Thanks to you and John for taking a look, I pushed the patch.
> 
> Simon
> 

Hi, 

I'm now seeing a build failure on powerpc.  (specifically ppc64le, but
i'm not sure it will matter which powerpc variant). 

First failure is 

...
  CXX    ppc-linux-nat.o
ppc-linux-nat.c: In function ‘int ppc_register_u_addr(gdbarch*, int)’:
ppc-linux-nat.c:658:22: error: ‘struct gdbarch_tdep’ has no member
named ‘ppc_gp0_regnum’
  658 |   if (regno >= tdep->ppc_gp0_regnum
...


Assorted other no-such-member errors follow. 



Thanks,
-Will


  reply	other threads:[~2021-11-15 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 20:42 Simon Marchi via Gdb-patches
2021-11-12 21:55 ` John Baldwin
2021-11-15 10:45 ` Luis Machado via Gdb-patches
2021-11-15 16:29   ` Simon Marchi
2021-11-15 20:42     ` will schmidt via Gdb-patches [this message]
2021-11-15 20:43       ` Simon Marchi via Gdb-patches
2021-11-15 23:19         ` Luis Machado via Gdb-patches
2021-11-16  2:02           ` Simon Marchi via Gdb-patches
2021-11-15 16:47 ` Pedro Alves
2021-11-15 16:53   ` 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=6f000cddd5fa3bb69f7321667a3aab83225531e9.camel@vnet.ibm.com \
    --to=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    --cc=luis.machado@linaro.org \
    --cc=simark@simark.ca \
    --cc=simon.marchi@efficios.com \
    --cc=will_schmidt@vnet.ibm.com \
    /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