Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>, Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH v2] Define an error function in the PPC simulator library.
Date: Tue, 05 Sep 2017 09:14:00 -0000	[thread overview]
Message-ID: <f90918d7-ae92-30d2-53d1-bc0d223009bd@redhat.com> (raw)
In-Reply-To: <8dcb1a42-4367-527e-1e5b-6f250c5e0e4c@FreeBSD.org>

On 09/05/2017 04:00 AM, John Baldwin wrote:
> On 9/4/17 7:19 AM, Pedro Alves wrote:
>> On 04/13/2017 06:18 PM, John Baldwin wrote:
>>> On Thursday, April 13, 2017 08:25:27 AM Luis Machado wrote:
>>>> On 04/05/2017 11:33 AM, John Baldwin wrote:
>>>>> Previously this used the error function from GDB directly when linked
>>>>> against GDB instead of the error method in the host callbacks
>>>>> structure.  This was exposed via a link error when GDB was converted
>>>>> to C++.  The error function invokes the error callback similar to
>>>>> sim_io_error.
>>>>>
>>>>
>>>> There is another implementation of error (...) in sim/ppc/main.c and 
>>>> sim/ppc/misc.c. Should those be kept as is or should we only use the new 
>>>> function you're providing?
>>>
>>> My understanding is that they should be kept as-is.  This file is only used
>>> when linking the library against GDB (and actually, rereading the log message,
>>> I should reword the opening sentence to make this clearer).  sim-calls.o isn't
>>> included in the actual library.  Each consumer of the library is required
>>> to export a couple of symbols that libsim.a uses including "error".  The dgen,
>>> igen, tmp-filter, tmp-ld-decode, tmp-ld-cache, and tmp-ld-insn programs use
>>> the functions from misc.c.  psim uses the functions from main.c, and
>>> GDB uses the functions from sim-calls.o.
>>
>> It'd be nice to include this info somewhere, likely in the commit log.
> 
> Will do.  Is there still time to merge this into 8.0.1 

I think the plan was yesterday, but it didn't happen yet, so I think
there's still time, though likely not much.

(and if so, can you approve it)?

Yes, I think it's safe.

You'll need to be sure that there's an entry for the issue
listed at:

 https://sourceware.org/gdb/wiki/GDB_8.0_Release

Either via the bugzilla query or explicitly listed.

Thanks,
Pedro Alves


  reply	other threads:[~2017-09-05  9:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 16:34 John Baldwin
2017-04-13 13:25 ` Luis Machado
2017-04-14 18:02   ` John Baldwin
2017-05-05 19:51     ` John Baldwin
2017-05-19 16:28       ` [PING] " John Baldwin
2017-06-06 17:49         ` John Baldwin
2017-06-23  6:39           ` Sebastian Huber
2017-09-04 14:19     ` Pedro Alves
2017-09-05  3:00       ` John Baldwin
2017-09-05  9:14         ` Pedro Alves [this message]
2017-09-05 11:46           ` John Baldwin
2017-09-05 19:38             ` Joel Brobecker

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=f90918d7-ae92-30d2-53d1-bc0d223009bd@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    --cc=lgustavo@codesourcery.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