Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: fche@redhat.com
Cc: hans-peter.nilsson@axis.com, gdb-patches@sourceware.org
Subject: Re: Committed, sim/cris: correct interrupt-preparation sequence for v32.
Date: Sun, 09 Apr 2006 17:00:00 -0000	[thread overview]
Message-ID: <200604091700.k39H0PLs003568@ignucius.se.axis.com> (raw)
In-Reply-To: <y0mzmiuu8zn.fsf@ton.toronto.redhat.com> (fche@redhat.com)

> From: fche@redhat.com (Frank Ch. Eigler)
> Date: 09 Apr 2006 10:19:40 -0400

> Hans-Peter Nilsson <hans-peter.nilsson@axis.com> writes:
> 
> > Stupid copy-paste-bug; when copying the interrupt-preparation code
> > from the (local-only) SID port, [...]
> 
> By the way, can you release the sid port instead of / in addition to
> this effort?

IIRC I mentioned in passing that there are issues why I didn't
do that: first of all, last time I looked and asked, the
copyright of SID wasn't FSF, but Red Hat, and contributors were
asked to assign copyright of major contributions to Red Hat.

Second, CGEN-SID has incompatibly (with src/sim) changed syntax
of the "delay" CGEN construct to the effect that it doesn't
support non-parallel machines with delay-slots anymore.  We can
discuss the latter on the CGEN list; the former I think I've
heard from someone (IIRC you in person, years ago) was subject
to change.

When/if those issues are fixed, it may seem more justifiable to
put time into updating the SID port and submitting it.  Maybe
I'll make a try at the CGEN issue, but Not Right Now.

brgds, H-P


  reply	other threads:[~2006-04-09 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 17:38 Hans-Peter Nilsson
2006-04-09 14:19 ` Frank Ch. Eigler
2006-04-09 17:00   ` Hans-Peter Nilsson [this message]
2006-04-09 17:06     ` Frank Ch. Eigler

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=200604091700.k39H0PLs003568@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=fche@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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