From: Joern Rennecke <amylaar@spamcop.net>
To: insight@sourceware.org
Cc: Richard Stuckey <Richard.Stuckey@arc.com>
Subject: Re: Where are the sources for insight 6.8?
Date: Mon, 09 Mar 2009 21:32:00 -0000 [thread overview]
Message-ID: <20090309173230.n3xz1r5o8wkwg84s-nzlynne@webmail.spamcop.net> (raw)
> I've never noticed that before! I use gdb's release method when doing
> the release, though, so I wonder if that directory is being excluded
> from gdb or if there is some sort of a bug w.r.t. to handling insight
> in the release process makefiles.
naked-cpu is part of the gdb-support module, which in turn is part of the
insight module.
I've now created insight_6_8-branchpoint and insight_6_8-branch
to cover all of the insight module. Release-generated files are not in
there, though.
I tagged / branched arc-insight_6_8-branchpoint and arc-insight_6_8-branch
off there, but I also added naked-cgen to that tag/branch because it is
needed in order to re-generate the cgen-generated files.
So far, I've checked the code for the stand-alone ARCompact simulator on
that branch.
next reply other threads:[~2009-03-09 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 21:32 Joern Rennecke [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-06 14:08 Joern Rennecke
2009-03-06 17:32 ` Keith Seitz
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=20090309173230.n3xz1r5o8wkwg84s-nzlynne@webmail.spamcop.net \
--to=amylaar@spamcop.net \
--cc=Richard.Stuckey@arc.com \
--cc=insight@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).