public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32049] New: Support on x86_64 also kind=16
Date: Tue, 22 May 2007 20:47:00 -0000 [thread overview]
Message-ID: <bug-32049-13404@http.gcc.gnu.org/bugzilla/> (raw)
It would be great if kind=16 could also be supported on x86_64 besides the
kinds 4, 8 and 10. With this some legacy code could be run and we would catch
up with ifort, which support kind 4, 8 and 16. (16 with software emulation.)
Problems:
- software fp is still a bit incomplete
- Supporting kind = 10 and kind = 16 at the same time is not supported by
libgfortran.
For the current software floating point support, see:
http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01490.html
http://gcc.gnu.org/ml/gcc-patches/2007-04/msg00728.html
Support for __float128 (TFmode) IEEE quad type is
available via soft-fp library on x86_64 targets. The
support includes basic arithmetic operations (addition, subtraction,
negation, multiplication and division of __float128</code>
values), full set of IEEE comparisons between <code>__float128</code>
values, conversions to and from <code>float</code>, <code>double</code>
and <code>long double</code> floating point types, as well as
conversions to and from <code>signed</code> or
unsigned integer, signed or unsigned long integer and signed or
unsigned quad integer (TImode) types. Additionally, all
operations generate full set of IEEE exceptions and support full set
of IEEE rounding modes.
--
Summary: Support on x86_64 also kind=16
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32049
next reply other threads:[~2007-05-22 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 20:47 burnus at gcc dot gnu dot org [this message]
2007-05-31 11:56 ` [Bug fortran/32049] " fxcoudert at gcc dot gnu dot org
2007-05-31 21:45 ` ubizjak at gmail dot com
2007-06-01 0:53 ` jvdelisle at gcc dot gnu dot org
2007-06-01 2:52 ` kargl at gcc dot gnu dot org
2007-06-01 4:07 ` jvdelisle at gcc dot gnu dot org
2007-06-02 7:37 ` fxcoudert at gcc dot gnu dot org
2008-08-26 6:13 ` burnus at gcc dot gnu dot org
2010-06-08 20:42 ` fxcoudert at gcc dot gnu dot org
2010-08-27 21:24 ` fxcoudert at gcc dot gnu dot org
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=bug-32049-13404@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).