From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Paulo J. Matos" <pocmatos@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Software FP Support
Date: Tue, 30 Mar 2010 15:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1003301421570.3777@digraph.polyomino.org.uk> (raw)
In-Reply-To: <11b141711003300638w7eabf6a8v72f13026bffffb12@mail.gmail.com>
On Tue, 30 Mar 2010, Paulo J. Matos wrote:
> I have 16 BITS_PER_UNIT for this target, with 1 UNITS_PER_WORD. If I
> define FLOAT_TYPE_SIZE to be 32, then a float is an HFmode and it's
> not that gcc uses this.
> Defining BITS_PER_UNIT to 16 shouldn't generate problems inside the
> compiler given that GCC has generic treatment for these situations
The GCC support for BITS_PER_UNIT values other than 8 is extremely
bitrotten and parts of it have never worked; there are no such targets in
the GCC source tree, no patches are tested for such targets and it is easy
to have hidden dependencies on 8-bit bytes. It is very inadvisable to
make your first port one to such an unusual target; substantially more GCC
experience and expertise is needed for doing a port to a system different
from all supported systems and that challenges hidden assumptions in the
GCC code. There will be a large amount of work finding and fixing issues
related to non-8-bit bytes that will need doing before you have a working
integer port, and all that should be done before you look at
floating-point issues.
If seriously interested in fixing support for non-8-bit bytes, first
understand exactly what the C semantics are for such systems (including
how strings are meant to work). Then read my various past messages to the
GCC lists discussing aspects of support for such systems in GCC (which you
should be able to find for yourself in the list archives). Improving wide
string support for normal 8-bit-byte systems (so that optimization etc.
infrastructure can work with both wide and narrow strings) may be a useful
starting point for making some things work when the characters in narrow
strings are more than one host byte.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2010-03-30 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 13:29 Paulo J. Matos
2010-03-30 13:39 ` Joseph S. Myers
2010-03-30 13:55 ` Paulo J. Matos
2010-03-30 15:11 ` Joseph S. Myers [this message]
2010-03-30 15:49 ` Paulo J. Matos
2010-03-30 14:09 ` Paulo J. Matos
2010-03-30 14:29 ` Paulo J. Matos
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=Pine.LNX.4.64.1003301421570.3777@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=pocmatos@gmail.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).