From: "Frank Ch. Eigler" <fche@redhat.com>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: cgen@sourceware.org
Subject: Re: [Q] What should I do before I send patches?
Date: Wed, 03 Jun 2009 16:55:00 -0000 [thread overview]
Message-ID: <20090603165505.GB3131@redhat.com> (raw)
In-Reply-To: <D173E82F-74BC-4C5D-8149-15B04F791287@monami-software.com>
Hi -
> I hacked FR80 instructions support to fr30.cpu.
> I tested on gas and objdump and there seems no regression.
Depending on the size of the changes, you may need an FSF copyright
assignment for bfd etc.
> But cgen is used with sim and/or sid also. Should I test on them?
Ideally.
> Can I get testing how-to documents about cgen?
If the whole fr80 toolchain can be built, and thus you are able to run
gcc/gas/ld/binutils/gdb/sim tests against it all, you're all set.
- FChE
prev parent reply other threads:[~2009-06-03 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 2:55 Masaki Muranaka
2009-06-03 16:55 ` Frank Ch. Eigler [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=20090603165505.GB3131@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sourceware.org \
--cc=monaka@monami-software.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).