Re: Build error with GCC13 + newlib 4.1.0 - error: 'float_t' undeclared
Chris Packham <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <CAFOYHZCQK33Jqr4zykZnswfRi67GF1tRkM9LvcSKFYPfy+y24g@mail.gmail.com> |
On Sun, May 28, 2023 at 12:28 PM Joel Sherrill <[email protected]> wrote: > > > > On Sat, May 27, 2023, 7:02 PM Chris Packham <[email protected]> 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