From: Torbjorn SVENSSON <torbjorn.svensson@st.com>
To: Andrea Corallo <andrea.corallo@arm.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>,
"nd@arm.com" <nd@arm.com>
Subject: RE: [PATCH V2] Aarch32/64: Support __FLT_EVAL_METHOD__ values other than 0, 1, 2
Date: Mon, 4 Apr 2022 15:12:24 +0000 [thread overview]
Message-ID: <AM6PR10MB219780E2088A782F2E80356781E59@AM6PR10MB2197.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <gkr4k38aoj7.fsf_-_@arm.com>
Hello again,
Yes that was the chunk I meant.
Apparently, I did not read the code close enough. Now when I go back and look at it again, I suppose it's fine.
Sorry for the noise!
Kind regards,
Torbjörn
ST Restricted
-----Original Message-----
From: Andrea Corallo <andrea.corallo@arm.com>
Sent: den 4 april 2022 16:53
To: Torbjorn SVENSSON <torbjorn.svensson@st.com>
Cc: newlib@sourceware.org; nd@arm.com
Subject: Re: [PATCH V2] Aarch32/64: Support __FLT_EVAL_METHOD__ values other than 0, 1, 2
Torbjorn SVENSSON <torbjorn.svensson@st.com> writes:
> Hello,
>
> It would have been easier to review the patch if it was inline, but
> this will have to do anyway.
Hi Torbjorn,
sorry most mail readers easily show inline attacchaments of type
"text/plain" allowing for inline reply, at the same time this way they
can still retain the notion of attached file. This is how I rutinary
sent my patches to other GNU projects (including GCC) so far. Has
newlib some specific rule around this?
> I think there is a typo in math.h. Aren't you supposed to do "#ifndef" and not "#ifdef"?
I guess we are talking about this hunk?
#ifdef __epiphany__
diff --git a/newlib/libc/include/math.h b/newlib/libc/include/math.h
index ba1a8a17e..da056b5b6 100644
--- a/newlib/libc/include/math.h
+++ b/newlib/libc/include/math.h
@@ -158,6 +158,15 @@ extern int isnan (double);
#else
/* Implementation-defined. Assume float_t and double_t have been
* defined previously for this configuration (e.g. config.h). */
+
+ /* If __DOUBLE_TYPE is defined (__FLOAT_TYPE is then supposed to be
+ defined as well) float_t and double_t definition is suggested by
+ an arch specific header. */
+ #ifdef __DOUBLE_TYPE
+ typedef __DOUBLE_TYPE double_t;
+ typedef __FLOAT_TYPE float_t;
+ #endif
+ /* Assume config.h has provided these types. */
#endif
#else
/* Assume basic definitions. */
I believe the #ifdef is correct. As the comment suggests if
__DOUBLE_TYPE is defined we'll use it to define double_t otherwise we
assume is config.h has provided the type definition.
I'm reattaching the latest version of this patch with a typo fixed.
Thanks!
Andrea
next prev parent reply other threads:[~2022-04-04 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 8:39 [PATCH] " Andrea Corallo
2022-04-04 9:32 ` Torbjorn SVENSSON
2022-04-04 14:53 ` [PATCH V2] " Andrea Corallo
2022-04-04 15:12 ` Torbjorn SVENSSON [this message]
2022-04-08 10:09 ` Richard Earnshaw
2022-04-08 21:22 ` Jeff Johnston
2022-04-11 13:52 ` [PATCH V3] " Andrea Corallo
2022-04-11 16:01 ` Jeff Johnston
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=AM6PR10MB219780E2088A782F2E80356781E59@AM6PR10MB2197.EURPRD10.PROD.OUTLOOK.COM \
--to=torbjorn.svensson@st.com \
--cc=andrea.corallo@arm.com \
--cc=nd@arm.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).