From: "Doug Kwan (關振德)" <dougkwan@google.com>
To: "Mark Mitchell" <mark@codesourcery.com>, gcc-patches@gcc.gnu.org
Cc: "Jim Blandy" <jimb@codesourcery.com>
Subject: Re: [LTO][PATCH] Fix long double precision problem
Date: Mon, 17 Dec 2007 21:53:00 -0000 [thread overview]
Message-ID: <498552560712171318o3da22bcn8142a995111732b4@mail.gmail.com> (raw)
In-Reply-To: <4765FBC0.8020400@codesourcery.com>
Would that easier and less error prone if we just emit the precision?
I looked at the i386 and ia64 backend and found float types with
precisions 32, 64, 80, 82 and 128. I am not sure if there is an easy
way to do the search in an architecture-indepedent manner?
-Doug
2007/12/16, Mark Mitchell <mark@codesourcery.com>:
> That seems reasonable enough. I guess the LTO front end can process a
> complex type by dividing its size by two, and then searching for a
> matching integral or floating-point base type, and using that information.
next prev parent reply other threads:[~2007-12-17 21:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 7:05 Doug Kwan (關振德)
2007-12-05 10:52 ` Andrew Pinski
2007-12-05 12:55 ` Kenneth Zadeck
2007-12-05 14:56 ` Diego Novillo
2007-12-05 16:28 ` Doug Kwan (關振德)
2007-12-05 19:02 ` Andrew Pinski
2007-12-05 16:34 ` Mark Mitchell
2007-12-05 18:42 ` Doug Kwan (關振德)
2007-12-05 19:01 ` Doug Kwan (關振德)
2007-12-05 23:52 ` Mark Mitchell
2007-12-11 23:15 ` Doug Kwan (關振德)
2007-12-12 9:22 ` Mark Mitchell
2007-12-12 20:23 ` Doug Kwan (關振德)
2007-12-12 20:45 ` Mark Mitchell
2007-12-13 2:27 ` Doug Kwan (關振德)
2007-12-13 11:02 ` Andreas Schwab
2007-12-13 19:13 ` Doug Kwan (關振德)
2007-12-14 9:50 ` Andreas Schwab
2007-12-14 22:18 ` Doug Kwan (關振德)
2007-12-13 20:11 ` Jim Blandy
2007-12-13 20:40 ` Doug Kwan (關振德)
2007-12-13 22:43 ` Jim Blandy
[not found] ` <4765FBC0.8020400@codesourcery.com>
2007-12-17 21:53 ` Doug Kwan (關振德) [this message]
2007-12-18 4:29 ` Mark Mitchell
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=498552560712171318o3da22bcn8142a995111732b4@mail.gmail.com \
--to=dougkwan@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimb@codesourcery.com \
--cc=mark@codesourcery.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).