From: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 8.2 branch 2018-06-22 Update
Date: Mon, 25 Jun 2018 21:26:00 -0000 [thread overview]
Message-ID: <877emmmvqp.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180622140540.GC3128@adacore.com>
Joel Brobecker <brobecker@adacore.com> writes:
> Anything else?
Hello,
I'm still working on enabling more registers in powerpc, and there's a
chance it might be ready by the end of the week.
However, the number of new registers breaks a use case with tracepoints
due to an internal buffer size. I have submitted patches to improve this
[1], and I'm addressing the comments from Ulrich's review. These affect
the core parts of gdb, not only powerpc.
[1] https://sourceware.org/ml/gdb-patches/2018-06/msg00501.html
Thanks!
--
Pedro Franco de Carvalho
prev parent reply other threads:[~2018-06-25 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 14:05 Joel Brobecker
2018-06-22 14:10 ` Simon Marchi
2018-06-22 14:13 ` Joel Brobecker
[not found] ` <87fu1eep8o.fsf@redhat.com>
2018-06-22 18:22 ` Joel Brobecker
2018-06-22 20:41 ` Sergio Durigan Junior
2018-06-23 15:17 ` Philippe Waroquiers
2018-06-25 21:26 ` Pedro Franco de Carvalho [this message]
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=877emmmvqp.fsf@linux.vnet.ibm.com \
--to=pedromfc@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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