public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@gmail.com>
To: Newlib <newlib@sourceware.org>
Subject: gcc 14+ and m68k build failure
Date: Sun, 2 Jun 2024 10:58:25 -0500	[thread overview]
Message-ID: <CAF9ehCV-fcvPBC9ZXLL_VotqGYPPs70gmT19OjWGsvMNvFvvhw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]

Hi

GCC 14+ fail to build a few newlib targets. I am looking into m68k-rtems
(m68k-elf) first. If there is a common thread, it appears to be related to
targets which do not have long double in all multilibs.

First, how do you see more than "CC..file.c"?

The error for m68k starts with this:

ake[3]: Entering directory
'/home/joel/test-gcc/b-m68k-rtems6-gcc/m68k-rtems6/newlib'
  CC       libm/complex/libm_a-ccoshl.o
../../../gcc/newlib/libm/complex/ccoshl.c: In function 'ccoshl':
../../../gcc/newlib/libm/complex/ccoshl.c:43:13: error: implicit
declaration of function 'coshl'; did you mean 'coshf'?
[-Wimplicit-function-declaration]
   43 |         w = coshl(x) * cosl(y) + (sinhl(x) * sinl(y)) * I;
      |             ^~~~~
      |             coshf
../../../gcc/newlib/libm/complex/ccoshl.c:43:24: error: implicit
declaration of function 'cosl'; did you mean 'cosf'?
[-Wimplicit-function-declaration]
   43 |         w = coshl(x) * cosl(y) + (sinhl(x) * sinl(y)) * I;


I suspect that since only one multilib for m68k has multilib and that is
picked at compile time, the multilib here isn't enabling the prototypes for
long double. That idea seems right but the code doesn't seem to always
follow up to avoid trying to compile files like the above which assume long
double.

Ideas appreciated.

--joel

             reply	other threads:[~2024-06-02 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02 15:58 Joel Sherrill [this message]
2024-06-03 16:44 ` Hans-Bernhard Bröker
2024-06-04  1:02 ` Pietro Monteiro
2024-06-04  1:41   ` Pietro Monteiro

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=CAF9ehCV-fcvPBC9ZXLL_VotqGYPPs70gmT19OjWGsvMNvFvvhw@mail.gmail.com \
    --to=joel.sherrill@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).