public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34040] Support for DOUBLE_TYPE_SIZE != 64 targets
Date: Tue, 05 May 2009 08:18:00 -0000	[thread overview]
Message-ID: <20090505081808.16443.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34040-14721@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from fxcoudert at gcc dot gnu dot org  2009-05-05 08:18 -------
As far as I can say, the targets with this problem are: avr, bfin, h8300,
picochip and sh (for some subtargets of sh).

On avr, bfin, h8300 and picochip, we're doomed anyway because there is no
double-sized type at all. On sh, we could use long double math calls.

I'm making this into an enhancement; it will probably be very painful, because
most of the front-end assumes FLOAT_TYPE_SIZE == 32 and DOUBLE_TYPE_SIZE == 64.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fxcoudert at gcc dot gnu dot
                   |                            |org
           Severity|normal                      |enhancement
 GCC target triplet|sh-unknown-elf              |sh, avr, bfin, h8300,
                   |                            |picochip
           Priority|P3                          |P5
   Last reconfirmed|2007-11-16 23:42:54         |2009-05-05 08:18:07
               date|                            |
            Summary|relation between kinds and C|Support for DOUBLE_TYPE_SIZE
                   |types (for math builtins)   |!= 64 targets
                   |shouldn't be hardcoded      |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34040


  parent reply	other threads:[~2009-05-05  8:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 10:42 [Bug middle-end/34040] New: [4.3 Regression] ICE: in simplify_subreg, at simplify-rtx.c:4921 building libgfortran rask at gcc dot gnu dot org
2007-11-09 10:45 ` [Bug middle-end/34040] " rask at gcc dot gnu dot org
2007-11-09 18:49 ` [Bug rtl-optimization/34040] " pinskia at gcc dot gnu dot org
2007-11-12 19:21 ` ebotcazou at gcc dot gnu dot org
2007-11-12 19:21 ` ebotcazou at gcc dot gnu dot org
2007-11-12 21:06 ` [Bug fortran/34040] " ebotcazou at gcc dot gnu dot org
2007-11-13 12:28 ` fxcoudert at gcc dot gnu dot org
2007-11-14  4:02 ` kkojima at gcc dot gnu dot org
2007-11-16 23:43 ` fxcoudert at gcc dot gnu dot org
2007-11-17 17:10 ` [Bug fortran/34040] relation between kinds and C types (for math builtins) shouldn't be hardcoded fxcoudert at gcc dot gnu dot org
2007-11-18 10:27 ` kkojima at gcc dot gnu dot org
2008-03-30 20:00 ` pinskia at gcc dot gnu dot org
2008-06-15 15:12 ` fxcoudert at gcc dot gnu dot org
2009-04-10 20:44 ` dfranke at gcc dot gnu dot org
2009-05-05  8:18 ` fxcoudert at gcc dot gnu dot org [this message]
     [not found] <bug-34040-4@http.gcc.gnu.org/bugzilla/>
2012-03-08 22:17 ` [Bug fortran/34040] Support for DOUBLE_TYPE_SIZE != 64 targets kkojima at gcc dot gnu.org
2013-12-05 19:39 ` olegendo at gcc dot gnu.org
2015-09-05  4:05 ` olegendo at gcc dot gnu.org
2021-05-31 15:45 ` dominiq at lps dot ens.fr
2023-05-31 15:17 ` gjl at gcc dot gnu.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=20090505081808.16443.qmail@sourceware.org \
    --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).