From: Jim Wilson <wilson@specifixinc.com>
To: Anil Paranjape <AnilP1@KPITCummins.com>
Cc: gcc@gcc.gnu.org
Subject: RE: Ping : H8/300 ABI Document
Date: Mon, 05 Apr 2004 23:57:00 -0000 [thread overview]
Message-ID: <1081209431.1050.6.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <69595093233BB547BB70CF5E492B63F204D2B789@sohm.kpit.com>
On Fri, 2004-04-02 at 00:43, Anil Paranjape wrote:
> I am suggesting to change the description of "structure alignment" to proper one.
Your suggested wording is wrong. I think the current wording is better
than your replacement, because your replacement says nothing about
alignment of fields. I think the current one can be improved by
changing "a multiple of" to "at most"
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-04-05 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 8:44 Anil Paranjape
2004-04-05 23:57 ` Jim Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 13:10 Anil Paranjape
2004-04-01 20:58 ` Jim Wilson
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=1081209431.1050.6.camel@leaf.tuliptree.org \
--to=wilson@specifixinc.com \
--cc=AnilP1@KPITCummins.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).