From: Joel Sherrill <joel@rtems.org>
To: Chris Packham <judge.packham@gmail.com>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: Build error with GCC13 + newlib 4.1.0 - error: 'float_t' undeclared
Date: Sat, 27 May 2023 19:28:28 -0500 [thread overview]
Message-ID: <CAF9ehCWCkizPVM=hooMvkrOxtZ6nj16WkkUUSOyATLGLNBy0gg@mail.gmail.com> (raw)
In-Reply-To: <CAFOYHZCDJUVtpz-QF4gLPE62W056mqK7GEBVDU4gYvvD17OSGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On Sat, May 27, 2023, 7:02 PM Chris Packham <judge.packham@gmail.com> wrote:
> Hello from CT-NG,
>
> I user reported the following build error with newlib after GCC13.1
> was added recently
>
By any chance did the default version of C change in 13 versus what
worked.before?
FWIW It looks.like the bleeding edge RTEMS tool builds in our farm have
some issue with gdb. So I don't have a handy case to compare.
> src/newlib/newlib/libm/math/wf_log2.c:34:22: error: 'float_t'
> undeclared (first use in this function); did you mean 'float'?
> 34 | return (logf(x) / (float_t) M_LN2);
> | ^~~~~~~
> | float
>
> From what I've been able to follow so far this may have something to
> do with how FLT_EVAL_METHOD is defined. It's not really mentioned in
> the GCC docs as something that has changed but I wonder if it is
> perhaps implied by a C standard the default of which probably has
> changed.
>
> Does this ring any bells for anyone?
>
next prev parent reply other threads:[~2023-05-28 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 0:01 Chris Packham
2023-05-28 0:28 ` Joel Sherrill [this message]
2023-05-28 2:00 ` Chris Packham
2023-05-28 2:23 ` Chris Packham
2023-05-28 5:07 ` Brian Inglis
2023-05-28 6:11 ` Brian Inglis
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='CAF9ehCWCkizPVM=hooMvkrOxtZ6nj16WkkUUSOyATLGLNBy0gg@mail.gmail.com' \
--to=joel@rtems.org \
--cc=judge.packham@gmail.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).