From: Peter Barada <peter@the-baradas.com>
To: gcc@gcc.gnu.org
Cc: peter@the-baradas.com
Subject: Improvements for ColdFire v4
Date: Wed, 21 Jan 2004 06:36:00 -0000 [thread overview]
Message-ID: <20040121063230.BAE17990D5@baradas.org> (raw)
I've got some changes kicking around that suppor the extra
insructions and addressing modes of ColdFire v4/v4e that didn't make
it into Bernie's previous ColdFire integration.
Now that I have papers on file for GCC, which trees could my changes
go into(GCC-3.3, GCC-3.4, CVS head)?
I'm assuming that I need to generate a ChangeLog entry as well as a
patch against each tree? Is there a web page that describes *exactly*
what a submission to gcc-patches should look like(and how best to
write a ChangeLog entry)?
Is it too late in the cycle(for each tree) to get these changes in?
--
Peter Barada
peter@the-baradas.com
next reply other threads:[~2004-01-21 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 6:36 Peter Barada [this message]
2004-01-21 6:39 ` Andreas Jaeger
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=20040121063230.BAE17990D5@baradas.org \
--to=peter@the-baradas.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).