From: Nick Clifton <nickc@redhat.com>
To: rsandifo@cambridge.redhat.com
Cc: binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: CGEN patch
Date: Thu, 21 Dec 2000 10:20:00 -0000 [thread overview]
Message-ID: <200012211820.KAA25517@elmo.cygnus.com> (raw)
Hi Richard,
: This is a cgen-related binutils patch. Uncertain of the etiquette,
: I'm posting it to both the cgen and binutils lists.
This is the right thing to do. The bfd parts of the patch need to be
approved by a binutils maintainer and the cgen parts by a cgen
maintainer. Since the cgen parts require the bfd parts, posting them
together is the right approach.
: 2000-12-21 Richard Sandiford <rsandifo@redhat.com>
:
: * libbfd.c (bfd_get_bits): Added
: (bfd_put_bits): Likewise
: * bfd-in.h: Declared the above.
Approved and applied.
A couple of minor formatting points:
: + /* Byte swapping routines which take size and endiannes as arguments. */
Two spaces at the end of a comment.
: + bfd_vma bfd_get_bits PARAMS ((bfd_byte *, int, boolean));
: + void bfd_put_bits PARAMS ((bfd_vma, bfd_byte *, int, boolean));
: +
: \f
There is no need for a blank line before the ^L.
: + if (bits % 8 != 0)
: + abort();
A space between the function name and the opening parenthesis.
: + int index = big_p? bytes - i - 1 : i;
: + addr[index] = (bfd_byte) data;
A blank line between the declaration of variables and the start of the
statements.
One other point - bfd-in.h is used to generate bfd-in2.h, so in your
ChangeLog entry you ought to include:
bfd-in2.h: Regenerate.
(And of course if you were checking in this patch yourself you would
need to make sure that you did regenerate bfd-in2.h).
I will leave the cgen parts of you your patch to be approved by a cgen
maintainer.
Cheers
Nick
next reply other threads:[~2000-12-21 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 10:20 Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-21 8:24 Richard Sandiford
2000-12-21 10:45 ` Frank Ch. Eigler
2000-12-21 14:04 ` Doug Evans
2001-01-02 6:51 ` Richard Sandiford
2001-01-02 8:34 ` Frank Ch. Eigler
2001-01-03 2:52 ` Richard Sandiford
2001-01-03 7:10 ` Frank Ch. Eigler
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=200012211820.KAA25517@elmo.cygnus.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=rsandifo@cambridge.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).