public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "corsepiu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/21203] Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90 Date: Sat, 14 May 2005 08:34:00 -0000 [thread overview] Message-ID: <20050514083358.22632.qmail@sourceware.org> (raw) In-Reply-To: <20050425082043.21203.corsepiu@gcc.gnu.org> ------- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-14 08:33 ------- (In reply to comment #16) > Subject: Re: Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90 > > > On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote: > > > * f95 disqualifies ifselves from several embedded targets, if it can > > not be > > built/used on targets not supporting REAL8. IIRC, there even exist > > variants of > > major _targets_ (IIRC, powerpc, m68k) which do not support REAL8. > > IMO, this is a design flaw, which should be in your interest to be > > circumvented. > > Huh, PPC soft float supports REAL 8 still. Joel, do you recall the target in RTEMS which has 4-byte floats only? (We recently had an issue with it floating point context sizes related to it? IIRC, it had been a powerpc variant and we were forced to drop it because GCC doesn't support it. BTW1: IFAIK, there also exist sh-variants (target tuple *-single*) which don't have 8byte floats. RTEMS doesn't support them, so I've never tried to build fortran for then. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |joel at oarcorp dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21203
next prev parent reply other threads:[~2005-05-14 8:34 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-25 8:21 [Bug fortran/21203] New: " corsepiu at gcc dot gnu dot org 2005-04-25 13:33 ` [Bug fortran/21203] " pinskia at gcc dot gnu dot org 2005-04-25 14:34 ` corsepiu at gcc dot gnu dot org 2005-04-25 16:38 ` kargl at gcc dot gnu dot org 2005-04-25 17:15 ` corsepiu at gcc dot gnu dot org 2005-05-01 14:44 ` ert at roe dot ac dot uk 2005-05-05 17:25 ` ericw at evcohs dot com 2005-05-11 23:12 ` tobi at gcc dot gnu dot org 2005-05-13 7:56 ` corsepiu at gcc dot gnu dot org 2005-05-13 7:59 ` corsepiu at gcc dot gnu dot org 2005-05-13 18:48 ` kargl at gcc dot gnu dot org 2005-05-13 19:25 ` tobi at gcc dot gnu dot org 2005-05-13 20:34 ` pinskia at gcc dot gnu dot org 2005-05-13 21:30 ` kargl at gcc dot gnu dot org 2005-05-14 6:30 ` corsepiu at gcc dot gnu dot org 2005-05-14 7:00 ` corsepiu at gcc dot gnu dot org 2005-05-14 7:04 ` Andrew Pinski 2005-05-14 7:08 ` Andrew Pinski 2005-05-14 7:04 ` pinskia at physics dot uc dot edu 2005-05-14 7:08 ` pinskia at physics dot uc dot edu 2005-05-14 8:14 ` corsepiu at gcc dot gnu dot org 2005-05-14 8:34 ` corsepiu at gcc dot gnu dot org [this message] 2005-05-14 15:25 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2005-05-14 15:58 ` sgk at troutmask dot apl dot washington dot edu 2005-05-14 16:06 ` sgk at troutmask dot apl dot washington dot edu 2005-05-15 3:55 ` corsepiu at gcc dot gnu dot org 2005-05-15 18:49 ` toon at moene dot indiv dot nluug dot nl [not found] ` <12687093.1116061034131.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net> 2005-05-15 18:49 ` Toon Moene 2005-05-16 14:01 ` joel at oarcorp dot com 2005-05-16 14:05 ` corsepiu at gcc dot gnu dot org 2005-05-18 11:24 ` Tobias dot Schlueter at physik dot uni-muenchen dot de [not found] <bug-21203-9565@http.gcc.gnu.org/bugzilla/> 2006-02-12 18:47 ` tobi at gcc dot gnu dot org 2006-09-25 9:19 ` 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=20050514083358.22632.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: linkBe 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).