From: Doug Evans <dje@google.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] sim: cgen: namespace custom trace functions
Date: Mon, 22 Jun 2015 14:10:00 -0000 [thread overview]
Message-ID: <CADPb22RCF4gYMiFHZczxgzQsPhMjWPGoi6bJdduHF5dchqO=+w@mail.gmail.com> (raw)
In-Reply-To: <20150621184030.GA17734@vapier>
On Sun, Jun 21, 2015 at 1:40 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On 14 Jun 2015 06:49, Doug Evans wrote:
>> On Fri, Jun 12, 2015 at 2:11 AM, Mike Frysinger wrote:
>> > The cgen code declares some macros/funcs using the trace_xxx prefix, but
>> > the code isn't generic and only works with cgen targets. This is blocking
>> > the creation of new common trace functions.
>> >
>> > Let's blindly add cgen_xxx prefixes to all these symbols. Some already
>> > use this convention to avoid conflicts, so it makes sense to align them.
>> > In the future we might want to move some to the common trace core, but
>> > one thing at a time.
>> >
>> > I'm attaching the patch compressed because it's like 2MB in size. It's
>> > all pretty mechanical -- the large files were updated using `sed`.
>> >
>> > Committed.
>>
>> Heads up, a lot of these are generated files.
>> I'm happy to update the generator and regenerate these.
>
> sorry about that. i'm not terribly familiar with cgen, and the heavy use of
> scheme makes it unlikely to improve the situation :/. looks like you posted
> a patch though at this point.
Feel free to ask for help.
Plus for simple renamings like this it's not that hard.
[If I can keep my lunch down from the Perl that's been
dropped on gdb, I just can't feel bad for having asked people
to learn some Scheme. :-)]
prev parent reply other threads:[~2015-06-22 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 9:11 Mike Frysinger
2015-06-14 13:49 ` Doug Evans
2015-06-21 18:40 ` Mike Frysinger
2015-06-22 14:10 ` Doug Evans [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='CADPb22RCF4gYMiFHZczxgzQsPhMjWPGoi6bJdduHF5dchqO=+w@mail.gmail.com' \
--to=dje@google.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