From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Andrew Johnson <anj@aps.anl.gov>,
Joel Sherrill <joel.sherrill@oarcorp.com>,
howland@LGSInnovations.com
Cc: newlib@sourceware.org
Subject: Re: newlib ieeefp.h again
Date: Thu, 23 Mar 2017 06:59:00 -0000 [thread overview]
Message-ID: <58D37229.70306@embedded-brains.de> (raw)
In-Reply-To: <854be012-0f1f-b0bf-b7a8-bc615452fa0e@aps.anl.gov>
On 23/03/17 00:17, Andrew Johnson wrote:
> Hi Joel & Craig,
>
> Hopefully you remember this email conversation from November:
>
> https://sourceware.org/ml/newlib/2016/msg01117.html
>
> I just built the RTEMS master branch for the uC5282 BSP, and found the
> same problem with the ieeefp.h header when building EPICS Base using the
> result. I think I can explain what's happening.
>
> Newlib's setting for _LDBL_EQ_DBL (in newlib.h) needs to change based on
> the particular CPU being compiled for. Here's some evidence:
Yes, this definition of _LDBL_EQ_DBL is wrong, since it depends on the
multilib. For example we have in the GCC build tree:
grep _LDBL_EQ_DBL `find -name newlib.h`
./m68k-rtems4.12/m68040/softfp/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/m68040/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/m5208/newlib/newlib.h:#define _LDBL_EQ_DBL 1
./m68k-rtems4.12/m5329/newlib/newlib.h:#define _LDBL_EQ_DBL 1
./m68k-rtems4.12/m5206/newlib/newlib.h:#define _LDBL_EQ_DBL 1
./m68k-rtems4.12/m5407/newlib/newlib.h:#define _LDBL_EQ_DBL 1
./m68k-rtems4.12/softfp/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/m68000/newlib/targ-include/newlib.h:/* #undef
_LDBL_EQ_DBL */
./m68k-rtems4.12/m68000/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/newlib/targ-include/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/m5475/softfp/newlib/newlib.h:#define _LDBL_EQ_DBL 1
./m68k-rtems4.12/m5475/newlib/newlib.h:#define _LDBL_EQ_DBL 1
./m68k-rtems4.12/m68060/softfp/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/m68060/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/mcpu32/newlib/newlib.h:/* #undef _LDBL_EQ_DBL */
./m68k-rtems4.12/m5307/newlib/newlib.h:#define _LDBL_EQ_DBL 1
In the installation tree:
grep _LDBL_EQ_DBL `find -name newlib.h`
./m68k-rtems4.12/include/newlib.h:/* #undef _LDBL_EQ_DBL */
So, only one random newlib.h is copied to the installation tree,
therefore all newlib.h of the build tree must be identical.
I would move the _LDBL_EQ_DBL definition to <ieeefp.h> based on compiler
provided defines.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2017-03-23 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 23:17 Andrew Johnson
2017-03-23 6:59 ` Sebastian Huber [this message]
2017-03-23 16:19 ` Andrew Johnson
2017-03-23 20:05 ` Craig Howland
2017-03-23 20:23 ` Joel Sherrill
2017-03-23 20:59 ` Craig Howland
2017-03-23 21:03 ` Joel Sherrill
2017-03-24 6:05 ` Sebastian Huber
2017-03-24 15:46 ` Craig Howland
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=58D37229.70306@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=anj@aps.anl.gov \
--cc=howland@LGSInnovations.com \
--cc=joel.sherrill@oarcorp.com \
--cc=newlib@sourceware.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).