From: Joel Sherrill <joel@rtems.org>
To: Eric Blake <eblake@redhat.com>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: i386 and x86_64 fenv support
Date: Tue, 27 Aug 2019 13:45:00 -0000 [thread overview]
Message-ID: <CAF9ehCUhv7qVa_DhSTR5oMDYQZJFA83=R4g6gi9TDc3qMrH8Ng@mail.gmail.com> (raw)
In-Reply-To: <4ee23442-69d7-6b6c-62b5-f0b119c18cc3@redhat.com>
On Tue, Aug 27, 2019 at 8:37 AM Eric Blake <eblake@redhat.com> wrote:
>
> On 8/27/19 8:31 AM, Joel Sherrill wrote:
> > Hi
> >
> > Earlier we discussed moving the winsup fenv.h files to newlib. Splitting
> > winsup/cygwin/include/fenv.h to create a sys/fenv.h looks easy enough.
> > But I have some status and a question after tinkering with this code out
> > of tree and compiling with the RTEMS i386 and x86_64
> >
> > It includes winsup.h and wincap.h but it doesn't need them.
> >
> > It is a C++ file and changing it to C only resulted in needing to change
> > bool to int and true/false to 1/0. That should be OK.
>
> Why not use <stdbool.h>, so you don't have to change bool to int?
Good idea. That works.
Thank you.
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3226
> Virtualization: qemu.org | libvirt.org
>
next prev parent reply other threads:[~2019-08-27 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 13:32 Joel Sherrill
2019-08-27 13:37 ` Eric Blake
2019-08-27 13:45 ` Joel Sherrill [this message]
2019-08-27 15:39 ` Corinna Vinschen
2019-08-27 15:46 ` Joel Sherrill
2019-08-27 15:55 ` Corinna Vinschen
2019-08-27 17:11 ` Joseph Myers
2019-08-27 17:30 ` Joel Sherrill
2019-08-27 17:51 ` Howland, Craig D. - US via newlib
2019-08-27 19:48 ` Joseph Myers
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='CAF9ehCUhv7qVa_DhSTR5oMDYQZJFA83=R4g6gi9TDc3qMrH8Ng@mail.gmail.com' \
--to=joel@rtems.org \
--cc=eblake@redhat.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).