From: Mike Frysinger <vapier@gentoo.org>
To: Tom Tromey <tom@tromey.com>
Cc: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH/committed] sim: bpf/or1k: fix CGEN_TRACE_EXTRACT name
Date: Mon, 1 Feb 2021 09:51:45 -0500 [thread overview]
Message-ID: <YBgVgWu8Y39YudAE@vapier> (raw)
In-Reply-To: <87zh0n274c.fsf@tromey.com>
On 01 Feb 2021 07:30, Tom Tromey wrote:
> >>>>> "Mike" == Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Mike> We renamed these years ago, but it looks like the cgen core missed the
> Mike> TRACE_EXTRACT function, so these new ports still used the incompatible
> Mike> common name. Fix those ports to use the right func.
>
> OOC was this done by re-running cgen?
it was not. i've sent the cgen folks a patch to fix the generator.
-mike
prev parent reply other threads:[~2021-02-01 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 22:09 Mike Frysinger
2021-02-01 14:30 ` Tom Tromey
2021-02-01 14:51 ` Mike Frysinger [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=YBgVgWu8Y39YudAE@vapier \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).