From: James Murray <jsm@jsm-net.demon.co.uk>
To: Ian Lance Taylor <iant@google.com>
Cc: binutils@sourceware.org
Subject: Re: m68hc11 target / S12X / XGATE
Date: Mon, 31 Jan 2011 19:03:00 -0000 [thread overview]
Message-ID: <1296500748.1100.12.camel@jsm2> (raw)
In-Reply-To: <mcry661j5te.fsf@google.com>
OK, thanks for the tips. I'll work on those (assuming make test is
available in gcc-3.3.6)
As noted, I am and will continue to actively test the generated code on
real hardware. It runs my car.
For gcc, this target is working fine with a 3.3.6 derivative, but the
patches never fully made mainstream gcc - so even 3.4.0 is worthless.
I have made an attempt to forward port to recent gcc releases but got
nowhere in a hurry.
(A colleague of mine is looking at LLVM support instead.)
regards
James
prev parent reply other threads:[~2011-01-31 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 23:46 James Murray
2011-01-31 18:18 ` Ian Lance Taylor
2011-01-31 19:03 ` James Murray [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=1296500748.1100.12.camel@jsm2 \
--to=jsm@jsm-net.demon.co.uk \
--cc=binutils@sourceware.org \
--cc=iant@google.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).