public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: geoffk@redhat.com
Cc: cgen@sources.redhat.com
Subject: Urgent build problem with Re: patch to allow any character in keyword
Date: Fri, 15 Jun 2001 10:16:00 -0000	[thread overview]
Message-ID: <o5lmmtackk.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <200106140125.f5E1Pof07706.cygnus.local.cgen@thief.cygnus.com>

geoffk wrote:

: ===File ~/patches/cgen-keywordspecials.patch================
: Index: devo/opcodes/ChangeLog
: 2001-06-13  Geoffrey Keating  <geoffk@redhat.com>
: 
: 	* cgen-asm.c (cgen_parse_keyword): When looking for the
: 	boundaries of a keyword, allow any special characters
: 	that are actually in one of the allowed keyword.
: 	* cgen-opc.c (cgen_keyword_add): Add any special characters
: 	to the nonalpha_chars field.
: 
: Index: devo/cgen/ChangeLog
: 2001-06-13  Geoffrey Keating  <geoffk@redhat.com>
: 
: 	* desc.scm (<keyword> 'gen-defn): Add extra zero into
: 	CGEN_KEYWORD_ENTRY initializers.
: 
: Index: devo/include/opcode/ChangeLog
: 2001-06-13  Geoffrey Keating  <geoffk@redhat.com>
: 
: 	* cgen.h (cgen_keyword): Add nonalpha_chars field.


Oops, there is a big problem with this patch, and I think it will have
to be reverted for now.

This is because the cgen.h change is not compatible with previously
generated opcodes files.  That in turn requires that every single
existing cgen-based opcodes port has to be regenerated (and given a
test run, etc.)  at the same time.  This hasn't been done, and
therefore, builds of older ports now break.

So, Geoff, want to revert or regenerate/retest them all?

I'm sorry I didn't realize this yesterday.  This hassle suggests that
a solution that doesn't involve changing global structs should be
investigated.


- FChE

       reply	other threads:[~2001-06-15 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200106140125.f5E1Pof07706.cygnus.local.cgen@thief.cygnus.com>
2001-06-15 10:16 ` Frank Ch. Eigler [this message]
2001-06-15 13:30   ` Geoff Keating
2001-06-18 13:48     ` J. Johnston
2001-06-18 14:13       ` Geoff Keating
2001-06-19  1:03       ` Geoff Keating
2001-06-19 16:58         ` J. Johnston

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=o5lmmtackk.fsf@toenail.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=cgen@sources.redhat.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).