From: Doug Evans <dje@transmeta.com>
To: gdb@sources.redhat.com
Cc: wilson@tuliptree.org
Subject: regenerating cgen sim sources for gdb 6.0
Date: Fri, 20 Jun 2003 16:27:00 -0000 [thread overview]
Message-ID: <200306201627.JAA08872@casey.transmeta.com> (raw)
It'd be great if cgen sim sources were regenerated for 6.0.
I'd be uncomfortable with 6.0 being released without up to date files.
Ok if I get someone at Redhat to regenerate them and check them in?
The sims in question are m32r and i960.
While the m32r is still, pedantically speaking, obsolete
and the i960 has been deleted, both targets still exist
in the gcc tree and having a sim to vet gcc changes is enormously useful.
I gather the i960 is on the way out even in gcc land though.
If Jim's ok with deleting src/sim/i960 fine.
Otherwise, I think the files should be updated.
I've already verified that there's no regressions in the
gcc testsuite from gcc top-of-tree sources (as of a few days ago)
with the before/after i960-coff-run simulator.
next reply other threads:[~2003-06-20 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 16:27 Doug Evans [this message]
2003-06-20 18:45 ` Frank Ch. Eigler
2003-06-20 18:54 ` Doug Evans
2003-06-20 19:39 ` Andrew Cagney
2003-06-20 20:25 ` Doug Evans
2003-06-20 20:50 ` Andrew Cagney
2003-06-20 21:16 ` Doug Evans
2003-06-20 21:22 ` Doug Evans
2003-06-20 16:30 Doug Evans
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=200306201627.JAA08872@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=gdb@sources.redhat.com \
--cc=wilson@tuliptree.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