From: Doug Evans <dje@google.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Tom Tromey <tromey@redhat.com>,
GDB Development <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>
Subject: Re: A Proposal to Move to Git
Date: Wed, 04 Sep 2013 16:55:00 -0000 [thread overview]
Message-ID: <CADPb22RsWVgs+G5jmX-tuSC0dByOkFWVCWXAwtAg46MBJ5vjvg@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1308302130560.41348@arjuna.pair.com>
On Fri, Aug 30, 2013 at 7:05 PM, Hans-Peter Nilsson <hp@bitrange.com> wrote:
> On Fri, 30 Aug 2013, Joseph S. Myers wrote:
> [...]
>> As I noted in <http://gcc.gnu.org/ml/gcc/2011-03/msg00486.html>, cgen
>> doesn't appear to use the shared toplevel at all, so if it moves out of
>> src, it would just be the cgen directory moving without a copy of anything
>> at toplevel; with regard to binutils+gdb, it's just another build tool.
>
> Still, the work-flow of using it will change (for sure for
> cgen-generated binutils and sim files) and the new work-flow of
> cgen development (both of and with) will have to be tested and
> documented. For sim, that's --enable-cgen-maint which now'll
> require an argument. It seems it'd almost work already except
> it'd have to live in a subdir called "lib" below the argument
> dir, which seems unnecessary.
Hi. I didn't understand where "lib" came from so I checked.
The location of cgen is defined in src/opcodes/configure.in
and src/sim/common/acinclude.m4.
[Note to self: IWBN to combine them.]
I'm guessing you're referring to this line, in both files:
cgendir=${cgen_maint}/lib/cgen}.
We can probably change that if it's useful.
The current default is src/cgen, for reference sake.
prev parent reply other threads:[~2013-09-04 16:55 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 21:12 Tom Tromey
2013-08-20 21:16 ` Andrew Pinski
2013-08-20 21:26 ` Joseph S. Myers
2013-08-20 21:19 ` Joel Brobecker
2013-08-20 21:21 ` Paul_Koning
2013-08-20 22:59 ` Phil Muldoon
2013-08-21 15:05 ` Eli Zaretskii
2013-08-21 15:32 ` Andreas Schwab
2013-08-21 15:54 ` Eli Zaretskii
2013-08-26 8:05 ` Andreas Schwab
2013-08-21 18:40 ` Steinar Bang
2013-08-21 20:05 ` Eli Zaretskii
2013-08-21 20:38 ` Andreas Schwab
2013-08-22 18:56 ` Florian Weimer
2013-08-21 15:38 ` Steve Ellcey
2013-08-21 15:50 ` Joel Brobecker
2013-08-22 6:10 ` Tristan Gingold
2013-08-22 14:16 ` Richard Earnshaw
2013-08-22 14:25 ` Joel Brobecker
2013-08-22 14:39 ` Fred Cooke
2013-08-22 20:10 ` Mark Kettenis
2013-08-22 20:21 ` Fred Cooke
2013-08-22 20:22 ` David Miller
2013-08-22 20:48 ` Andrew Pinski
2013-08-22 21:07 ` Andreas Schwab
2013-08-22 21:10 ` Tom Tromey
2013-08-23 15:40 ` H.J. Lu
2013-08-23 15:55 ` Joel Brobecker
2013-08-23 16:03 ` Paul_Koning
2013-08-23 16:05 ` H.J. Lu
2013-08-26 12:37 ` NightStrike
[not found] ` <upzc38pvcv1w.fsf@dod.no>
2013-08-27 16:21 ` asmwarrior
2013-08-23 16:03 ` H.J. Lu
2013-08-23 16:09 ` Joel Brobecker
2013-08-23 16:24 ` Matt Rice
2013-08-23 16:37 ` H.J. Lu
2013-08-23 16:47 ` Matt Rice
2013-08-23 17:01 ` H.J. Lu
[not found] ` <87siy070su.fsf@dod.no>
2013-08-24 0:27 ` Doug Evans
2013-08-22 23:55 ` Alan Modra
2013-08-30 22:58 ` Hans-Peter Nilsson
2013-08-30 23:37 ` Joseph S. Myers
2013-08-31 2:05 ` Hans-Peter Nilsson
2013-08-31 16:58 ` Joseph S. Myers
2013-09-04 16:55 ` 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=CADPb22RsWVgs+G5jmX-tuSC0dByOkFWVCWXAwtAg46MBJ5vjvg@mail.gmail.com \
--to=dje@google.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hp@bitrange.com \
--cc=joseph@codesourcery.com \
--cc=tromey@redhat.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