From: Doug Evans <dje@google.com>
To: cgen@sourceware.org, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [CGEN PATCH] Rename TRACE_{EXTRACT,RESULT} to CGEN_TRACE_{EXTRACT,RESULT}
Date: Fri, 19 Jun 2015 14:37:00 -0000 [thread overview]
Message-ID: <CADPb22QnfcKHRNdHECeVUar526-gQ5t9GmhZULwPjW5mBKFvrg@mail.gmail.com> (raw)
In-Reply-To: <20cf303dda3c40d2610518cfe377@google.com>
On Thu, Jun 18, 2015 at 2:33 PM, Doug Evans <dje@google.com> wrote:
> [sorry for the repost, typo in email address]
>
> Hi.
>
> This patch updates the generator so that the next time
> the files are generated we don't lose the TRACE_{EXTRACT,RESULT}
> renaming change.
>
> ref:
> https://sourceware.org/ml/gdb-patches/2015-06/msg00280.html
>
> Tested with:
>
> 1) put guile 1.8.8 in $PATH
>
> 2) apply this patch:
>
> https://sourceware.org/ml/gdb-patches/2015-06/msg00395.html
>
> 3)
>
> bash$ $src/configure --prefix=$(pwd)/rel \
> --enable-cgen-maint \
> --enable-targets=all \
> --enable-sim
> bash$ make all-sim
Darn, I wanted these steps to be complete.
Missed a step, so let me try again.
1) put guile 1.8.8 in $PATH
[no special configure options are needed, just --prefix]
2) check out cgen
bash$ cd /place/to/put/cgen
bash$ cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co cgen
2b) make sure the build can find it
bash$ ln -s $(pwd)/src/cgen $git/cgen
There's a TODO to be able to specify the path to cgen
when configuring binutils,gdb.
I've always just done this hack when I need it.
3) apply this patch
https://sourceware.org/ml/gdb-patches/2015-06/msg00395.html
4) Build all the sims.
Generated files that need regenerating will be,
including the opcodes files.
bash$ cd $build
bash$ $git/configure --prefix=$(pwd)/rel \
--enable-cgen-maint \
--enable-targets=all \
--enable-sim
bash$ make all-sim
If/when some form of (3) gets applied, and the TODO is done,
the steps should be simple enough.
Heads up, if you try this today there are two other outstanding patches
to cgen that affect the generated files.
next prev parent reply other threads:[~2015-06-19 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 19:33 Doug Evans
2015-06-19 14:37 ` Doug Evans [this message]
2015-06-21 18:43 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2015-06-18 19:33 Doug Evans
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=CADPb22QnfcKHRNdHECeVUar526-gQ5t9GmhZULwPjW5mBKFvrg@mail.gmail.com \
--to=dje@google.com \
--cc=cgen@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).