From: Neil Booth <neil@daikokuya.co.uk>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: 3.4BIB HOST_WIDE_INT size error
Date: Sat, 14 Dec 2002 01:54:00 -0000 [thread overview]
Message-ID: <20021214095357.GA534@daikokuya.co.uk> (raw)
In-Reply-To: <20021214072209.GA14091@doctormoo>
Nathanael Nerode wrote:-
> The lazy-proper fix (if I can call it that?) is to introduce a
> single-precision library for constant integers in tree, RTL, and cpp.
In 3.3., CPP already gets this stuff right. It just doesn't handle the
case where the widest target int is strictly greater than twice the
widest host int. Since this is almost never the case, I didn't deem
it worthwhile doing truly MP stuff.
However, if we do go to arbitrary arithmetic, which would be nice
aestetically at least, we *must not* impact the performance of native
compiles. Since all this is theoretically determinable at build
time, there should be no run-time performance hit for handling native
efficiently, and crosses less efficiently if the target types make
that necessary.
> Maybe I'll put this on the beginner projects list, since it's another
> BUILD/HOST/TARGET confusion issue.
I think if you can solve these issues you're a bit more advanced than
"beginner" 8-)
Neil.
next prev parent reply other threads:[~2002-12-14 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 23:23 Nathanael Nerode
2002-12-13 23:36 ` Zack Weinberg
2002-12-14 1:54 ` Neil Booth [this message]
2002-12-15 12:57 ` Kai Henningsen
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 22:49 Nathanael Nerode
2002-12-13 23:09 ` Zack Weinberg
2002-12-17 13:07 ` Alexandre Oliva
2002-12-11 15:01 David Edelsohn
2002-12-11 15:09 ` Zack Weinberg
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=20021214095357.GA534@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=neroden@twcny.rr.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).