From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org, vapier@gentoo.org
Subject: Re: [PATCH 1/2] sim/opcodes: Allow use of out of tree cgen source directory
Date: Tue, 27 Nov 2018 11:21:00 -0000 [thread overview]
Message-ID: <20181127112112.GC2834@embecosm.com> (raw)
In-Reply-To: <c909aa552d84af20ca6765341922bb09@polymtl.ca>
* Simon Marchi <simon.marchi@polymtl.ca> [2018-11-26 16:07:35 -0500]:
> On 2018-11-06 12:35, Andrew Burgess wrote:
> > diff --git a/opcodes/configure.ac b/opcodes/configure.ac
> > index 4c3698356b..9e48fedf9a 100644
> > --- a/opcodes/configure.ac
> > +++ b/opcodes/configure.ac
> > @@ -109,11 +109,21 @@ AC_ARG_ENABLE(cgen-maint,
> > yes) cgen_maint=yes ;;
> > no) cgen_maint=no ;;
> > *)
> > - # argument is cgen install directory (not implemented yet).
> > - # Having a `share' directory might be more appropriate for the .scm,
> > - # .cpu, etc. files.
> > + # Argument is a directory where cgen can be found. In some
> > + # future world cgen could be installable, but right now this
> > + # is not the case. Instead we assume the directory is a path
> > + # to the cgen source tree.
> > cgen_maint=yes
> > - cgendir=${cgen_maint}/lib/cgen
> > + if test -r ${enableval}/iformat.scm; then
> > + # This looks like a cgen source tree.
> > + cgendir=${enableval}
> > + else
> > + # This code would handle a cgen install. For now we assume
> > + # 'lib', but this is really just a place holder. Maybe
> > + # having a `share' directory might be more appropriate for
> > + # the .scm, .cpu, etc. files.
> > + cgendir=${enableval}/lib/cgen
> > + fi
> > ;;
> > esac])dnl
> > AM_CONDITIONAL(CGEN_MAINT, test x${cgen_maint} = xyes)
>
> Just wondering, does the "else" part have any real-world use? Before today,
> was there any reason to pass a path to --enable-cgen-maint ?
Thanks for taking a look at this patch :)
Not as far as I can tell. I left it in just in case, but as far as I
can tell there's no way to "install" CGEN. I'd be happy to drop the
../lib/cgen references (the else block) completely, and then validate
that we have a CGEN source tree or error.... But the above seemed like
the least invasive change.
Andrew
next prev parent reply other threads:[~2018-11-27 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 17:35 [PATCH 0/2] Allow use of out-of-tree CGEN source Andrew Burgess
2018-11-06 17:35 ` [PATCH 1/2] sim/opcodes: Allow use of out of tree cgen source directory Andrew Burgess
2018-11-26 21:07 ` Simon Marchi
2018-11-27 11:21 ` Andrew Burgess [this message]
2018-11-27 19:47 ` Simon Marchi
2018-11-27 20:03 ` John Baldwin
2018-11-29 19:01 ` Tom Tromey
2018-11-27 20:27 ` Andrew Burgess
2018-11-27 20:31 ` Simon Marchi
2018-11-30 19:07 ` Andrew Burgess
2018-11-30 19:50 ` Tom Tromey
2018-11-06 17:35 ` [PATCH 2/2] sim/cris: Fix references to cgen cpu directory Andrew Burgess
2018-11-30 19:51 ` Tom Tromey
2018-11-26 15:17 ` [PATCH 0/2] Allow use of out-of-tree CGEN source Andrew Burgess
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=20181127112112.GC2834@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=vapier@gentoo.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