public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/36939] Build Failure Ada SH2e
Date: Mon, 07 Feb 2011 14:37:00 -0000	[thread overview]
Message-ID: <bug-36939-4-4JQFNC5YhM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36939-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Joel Sherrill <joel at gcc dot gnu.org> 2011-02-07 14:22:20 UTC ---
(In reply to comment #17)
> > With Laurent's stub version of s-scaval.adb added as s-scaval-sh.adb and a
> > minor change to a ada/gcc-interface/Makefile.in, sh-rtems now builds
> > Ada.
> > 
> > Is this OK to commit?
> 
> Note that the proper place to submit a patch officially is gcc-patches.
> 
> In any case, adding s-scaval-sh.adb isn't OK, s-scaval.adb isn't meant to
> have target specific implementations, or stubbed implementation, that's
> a kludge which is not really acceptable for mainstream.

I didn't like this solution but it does let the target compile.

But the underlying problem is more general.  How should targets with only
single precision floating point be supported by s-scaval.adb?  I am pretty sure
there  is currently a PowerPC e500 core with only single precision.  

> Arno


  parent reply	other threads:[~2011-02-07 14:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36939-4@http.gcc.gnu.org/bugzilla/>
2011-02-07  0:34 ` joel at gcc dot gnu.org
2011-02-07  9:04   ` Arnaud Charlet
2011-02-07  1:20 ` joel at gcc dot gnu.org
2011-02-07  6:48 ` laurent at guerby dot net
2011-02-07  9:05 ` charlet at adacore dot com
2011-02-07 14:37 ` joel at gcc dot gnu.org [this message]
2011-02-07 17:43 ` joel at gcc dot gnu.org
2011-02-07 21:46 ` laurent at guerby dot net
2011-02-07 22:38 ` joel at gcc dot gnu.org
2013-12-05 19:53 ` olegendo at gcc dot gnu.org
2008-07-25 19:42 [Bug ada/36939] New: " joel at gcc dot gnu dot org
2008-07-25 19:53 ` [Bug ada/36939] " laurent at guerby dot net
2008-07-25 20:05 ` laurent at guerby dot net
2008-07-25 20:36 ` joel at gcc dot gnu dot org
2008-07-25 20:47 ` laurent at guerby dot net
2008-07-25 20:54 ` joseph at codesourcery dot com
2008-12-02 14:04 ` joel at gcc dot gnu dot org
2008-12-10 11:58 ` laurent at guerby dot net
2008-12-10 18:09 ` joel at gcc dot gnu dot org
2008-12-10 19:16 ` joel at gcc dot gnu dot org
2008-12-10 23:11 ` laurent at guerby dot net
2009-02-27 16:24 ` joel at gcc dot gnu dot org
2009-02-27 17:50 ` laurent at guerby dot net
2009-03-23 22:14 ` joel 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-36939-4-4JQFNC5YhM@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).