From: Nathan Sidwell <nathan@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: Target ABIs with 16bit ints.
Date: Mon, 14 Oct 2002 12:56:00 -0000 [thread overview]
Message-ID: <3DAB1BA8.9080702@codesourcery.com> (raw)
Hi,
Something's just popped concerning targets with 16bit ints. Paul Koning
reminds me that the pdp11 target has such. This conflicts with the gcc
& gnu coding standards.
doc/portability.texi says
'The main goal of GCC was to make a good, fast compiler for machines in
the class that the GNU system aims to run on: 32-bit machines that address
8-bit bytes and have several general registers.'
the gnu coding standards additionally say
'However, don't make any effort to cater to the possibility that an
@code{int} will be less than 32 bits. We don't support 16-bit machines
in GNU.'
How many 16bit int abi targets do we have?
How important are they now? (Yes, I know the pdp11 /was/ important :)
Should we deprecate them?
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2002-10-14 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 12:56 Nathan Sidwell [this message]
2002-10-14 14:06 ` DJ Delorie
2002-10-14 14:06 ` Nathan Sidwell
2002-10-14 16:12 ` Michael Matz
2002-10-14 16:29 ` Michael Matz
2002-10-15 0:22 ` Mike Laman
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=3DAB1BA8.9080702@codesourcery.com \
--to=nathan@codesourcery.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).