public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Alan Lehotsky <apl@alum.mit.edu>
To: Ben Elliston <bje@redhat.com>
Cc: lehotsky@earthlink.net, cgen@sourceware.cygnus.com
Subject: Re: debugging help?
Date: Tue, 08 May 2001 17:12:00 -0000	[thread overview]
Message-ID: <p04330109b71e3ad79196@[192.168.1.254]> (raw)
In-Reply-To: <15096.33343.222519.11808@scooby.apac.redhat.com>

At 9:33 AM +1000 5/9/01, Ben Elliston wrote:

> >>>>> "lehotsky" == lehotsky  <lehotsky@earthlink.net> writes:
>
>  lehotsky> the cgen code doesn't seem to issue very useful error messages.
>  lehotsky> Any suggestions on how to track down this problem?
>
>I see Frank has already answered, this, however ..
>
>  lehotsky> Computing sformat argument buffers ...
>  lehotsky> ERROR: bad bitsize argument to gen-ifetch 4
>  lehotsky> No backtrace available.
>  lehotsky> make[1]: *** [cgen-cpu-decode] Error 1
>
>It so happens that I recognise this one.  It is often caused by
>instruction formats (the "(+ ...)" clause) missing one or more
>bits--or containing overlapping ifields.
>
>Ben


	And you're right.  I had looked at all my (+ ....) patterns and discovered that
	I had entered the SAME field twice!  If I was a "schemer" (or a conniver - sorry, old
	MIT joke....), I'd try to write code that would identify that case and issue a better warning
	message.

	Frankly, I like the cgen "language", but the error diagnostics REALLY are terrible.
	It takes a lot of fumbling around to figure out what it's really complaining about most of the
	time.....

-- Al
-- 
------------------------------------------------------------------------

		    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

      parent reply	other threads:[~2001-05-08 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08  9:49 lehotsky
2001-05-08 10:08 ` Frank Ch. Eigler
2001-05-08 16:33 ` Ben Elliston
2001-05-08 16:36   ` Marc Esipovich
2001-05-08 20:16     ` Ben Elliston
2001-05-08 17:12   ` Alan Lehotsky [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='p04330109b71e3ad79196@[192.168.1.254]' \
    --to=apl@alum.mit.edu \
    --cc=bje@redhat.com \
    --cc=cgen@sourceware.cygnus.com \
    --cc=lehotsky@earthlink.net \
    /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).