From: Chris Packham <judge.packham@gmail.com>
To: joel@rtems.org
Cc: Newlib <newlib@sourceware.org>
Subject: Re: Build error with GCC13 + newlib 4.1.0 - error: 'float_t' undeclared
Date: Sun, 28 May 2023 14:23:23 +1200 [thread overview]
Message-ID: <CAFOYHZDYAfEDOSei_kvP+XDMWVm93P+zKb8DKCLaf1ha5QK6BA@mail.gmail.com> (raw)
In-Reply-To: <CAFOYHZCQK33Jqr4zykZnswfRi67GF1tRkM9LvcSKFYPfy+y24g@mail.gmail.com>
On Sun, May 28, 2023 at 2:00 PM Chris Packham <judge.packham@gmail.com> wrote:
>
> On Sun, May 28, 2023 at 12:28 PM Joel Sherrill <joel@rtems.org> wrote:
> >
> >
> >
> > 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.
> >
>
> https://gcc.gnu.org/gcc-13/changes.html doesn't mention it explicitly
> but I wouldn't be surprised if it has.
>
> >>
> >> 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?
>
> I'll also add that I've now double checked the same configuration
> works with GCC 12.2
Looks like the following two upstream newlb changes might help
https://sourceware.org/git?p=newlib-cygwin.git;a=commit;h=91f99d323b39dc0c06c40038791db9861d4b76b9
https://sourceware.org/git?p=newlib-cygwin.git;a=commit;h=27f0913c17c216548b2f5eea79037ee90038f375
Which leads into another question. ct-ng currently has newlib-4.1.0.
Looking at https://sourceware.org/ftp/newlib/index.html are the 4.2.0
and 4.3.0 dated snapshots the actual release or are they release
candidates?
next prev parent reply other threads:[~2023-05-28 2:23 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
2023-05-28 2:00 ` Chris Packham
2023-05-28 2:23 ` Chris Packham [this message]
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=CAFOYHZDYAfEDOSei_kvP+XDMWVm93P+zKb8DKCLaf1ha5QK6BA@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=joel@rtems.org \
--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).