From: "Frank Ch. Eigler" <fche@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: brolley@redhat.com, gdb-patches@sourceware.org, cgen@sourceware.org
Subject: Re: sim/frv not regeneratable with cgen and guile-1.8.5
Date: Tue, 23 Dec 2008 17:32:00 -0000 [thread overview]
Message-ID: <20081223173148.GD4195@redhat.com> (raw)
In-Reply-To: <200812230143.mBN1hm8O020799@ignucius.se.axis.com>
Hi -
On Tue, Dec 23, 2008 at 02:43:48AM +0100, Hans-Peter Nilsson wrote:
> I had to find an installation with guile-1.3.4 in order to
> regenerate the frv sim. Maybe a guile/scheme-savvy
> person/maintainer can look into it? I had to give up myself,
> sorry. CGEN and guile..lacks in the debuggability department.
It's clumsy. Changing the sim/.../Makefile thusly activated
backtracing:
CGEN = "`if [ -f ../../guile/libguile/guile ]; then echo ../../guile/libguile/guile; else echo guile ; fi` -l $(CGENDIR)/guile.scm --debug -s"
CGENFLAGS = -v -b
The operative flags being "--debug" for guile *and* "-b" for cgen.
Perhaps we should simply activate these all the time, machines being
fast enough.
The following patch, committed, fixes cgen for frv; tested also on m32r.
2008-12-23 Frank Ch. Eigler <fche@redhat.com>
* sim.scm (-op-gen-queued-write): Add needed symbol->string.
Index: sim.scm
===================================================================
RCS file: /cvs/src/src/cgen/sim.scm,v
retrieving revision 1.14
diff -r1.14 sim.scm
1147c1147
< (string-downcase (if sem-mode
---
> (string-downcase (symbol->string (if sem-mode
1149c1149
< (mode-real-name mode))))))
---
- FChE
prev parent reply other threads:[~2008-12-23 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 1:45 Hans-Peter Nilsson
2008-12-23 17:32 ` Frank Ch. Eigler [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=20081223173148.GD4195@redhat.com \
--to=fche@redhat.com \
--cc=brolley@redhat.com \
--cc=cgen@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=hans-peter.nilsson@axis.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).