public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: cgen@sources.redhat.com, hp@axis.com
Subject: Re: m32r port breakage
Date: Wed, 18 Dec 2002 09:10:00 -0000	[thread overview]
Message-ID: <15872.44029.466573.783431@casey.transmeta.com> (raw)
In-Reply-To: <m3pts05i0p.fsf@scooby.brisbane.redhat.com>

Ben Elliston writes:
 >   Doug> Why was @PREFIX@_INSN_MAX replaced with "last instruction enum plus one"?
 > 
 > A port I was doing had an instruction called "MAX" that generated the
 > symbol @PREFIX@_INSN_MAX.  Rather than change the name of the sentinel
 > value, I decided to clean this up to avoid any further problems.  I
 > guess I got carried away. :-( Perhaps you could change the sentinel
 > value's name to @PREFIX@_INSN__MAX?

Let's do that.

      reply	other threads:[~2002-12-18 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  0:38 Doug Evans
2002-12-17 15:43 ` Ben Elliston
2002-12-18  9:10   ` 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=15872.44029.466573.783431@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=bje@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=hp@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).