From: Alan Lehotsky <apl@alum.mit.edu>
To: Geoff Keating <geoffk@redhat.com>
Cc: apl@alum.mit.edu, cgen@sourceware.cygnus.com
Subject: Re: Can't see what's wrong with my simulator semantics code....
Date: Sat, 30 Jun 2001 12:35:00 -0000 [thread overview]
Message-ID: <p04330108b763d9edc132@[192.168.1.254]> (raw)
In-Reply-To: <200106301941.MAA05669@geoffk.org>
At 12:41 PM -0700 6/30/01, Geoff Keating wrote:
> > Date: Sat, 30 Jun 2001 15:09:59 -0400
>> From: Alan Lehotsky <apl@alum.mit.edu>
>> Cc: apl@alum.mit.edu (Alan Lehotsky), cgen@sourceware.cygnus.com
>
>> cgen is really "cool" when you don't have to fight the error messages.
>
>Yeah. Line numbers would be a Really Useful Feature.
>
>--
>- Geoffrey Keating <geoffk@geoffk.org>
You do know about adding "-v" to the CGENFLAGS when you do a make of the
simulator. It tells you some stuff that helps isolate where the errors are.
Also, the old tried and true technique of inserting KNOWN errors to see if the
parser finds the old error before your new error helps to isolate problems.....
--
------------------------------------------------------------------------
Quality Software Management
http://home.earthlink.net/users/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
(978)287-0436 Fax
Software Process Improvement and Management Consulting
Language Design and Compiler Implementation
next prev parent reply other threads:[~2001-06-30 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <p04330101b763b6596543.cygnus.local.cgen@[192.168.1.254]>
2001-06-30 11:55 ` Geoff Keating
2001-06-30 12:10 ` Alan Lehotsky
2001-06-30 12:25 ` Geoff Keating
2001-06-30 12:35 ` Alan Lehotsky [this message]
2001-06-30 17:12 ` Ben Elliston
2001-06-30 10:20 Alan Lehotsky
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='p04330108b763d9edc132@[192.168.1.254]' \
--to=apl@alum.mit.edu \
--cc=cgen@sourceware.cygnus.com \
--cc=geoffk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).