From: Jim Blandy <jimb@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: josh wojnas <josh_wolf@yahoo.com>,
"insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: is there any chance insight could work for gcc compileing for the pic microprossesor?
Date: Wed, 17 Dec 2003 22:10:00 -0000 [thread overview]
Message-ID: <vt2iskfjdyd.fsf@zenia.home> (raw)
In-Reply-To: <1071596564.1589.3.camel@lindt.uglyboxes.com>
Keith Seitz <keiths@redhat.com> writes:
> On Mon, 2003-12-15 at 19:54, josh wojnas wrote:
> > is there any chance insight could work for gcc compileing for the pic microprossesor?
>
> If gdb supports it, so would insight. I would ask on the gdb mailing
> list (gdb@sources.redhat.com): they would be the definitive authorities
> on this.
The GNU toolchain doesn't seem to support the PIC at all. I don't see
any mention of it in gcc/config, or in bfd/bfd-in2.h.
For what it's worth, if you like high-level languages, one of Marc
Feeley's graduate students has implement Scheme on the PIC. There are
links from here:
http://www.iro.umontreal.ca/~feeley/
prev parent reply other threads:[~2003-12-17 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 3:54 josh wojnas
2003-12-16 17:38 ` Keith Seitz
2003-12-17 22:10 ` Jim Blandy [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=vt2iskfjdyd.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=insight@sources.redhat.com \
--cc=josh_wolf@yahoo.com \
--cc=keiths@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).