public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109814] [13/14 Regression] freestanding using cmath does not compile anymore
Date: Fri, 28 Jul 2023 10:54:49 +0000	[thread overview]
Message-ID: <bug-109814-4-D8NdXmkE7Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109814-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109814

--- Comment #13 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #12)

> I suppose we could enable <cmath> if hosted || newlib, but that wouldn't
> always be right because (IIUC) you can configure newlib without any of the
> libm functions. I suppose if you use such a newlib and then include <cmath>
> that's your own fault and you get to keep both pieces.

that seems reasonable, though my thinking is that maybe we can bring newlib
closer to hosted in general.  it even features C buffered IO (AFAIU) and
malloc, so it could provide the stuff that 'blocks' other features from working
on freestanding (besides threading, presumably?  I'd need to check what exactly
newlib provides)

  parent reply	other threads:[~2023-07-28 10:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 15:27 [Bug libstdc++/109814] New: " lestofante88 at gmail dot com
2023-05-11 15:38 ` [Bug libstdc++/109814] " xry111 at gcc dot gnu.org
2023-05-11 15:52 ` redi at gcc dot gnu.org
2023-05-11 15:58 ` [Bug libstdc++/109814] [13/14 Regression] " redi at gcc dot gnu.org
2023-05-11 16:00 ` redi at gcc dot gnu.org
2023-05-11 16:48 ` lestofante88 at gmail dot com
2023-05-11 17:43 ` redi at gcc dot gnu.org
2023-05-11 19:22 ` arsen at gcc dot gnu.org
2023-05-11 19:29 ` pinskia at gcc dot gnu.org
2023-05-12 20:04 ` lestofante88 at gmail dot com
2023-05-12 22:34 ` arsen at gcc dot gnu.org
2023-05-16 20:44 ` pinskia at gcc dot gnu.org
2023-07-27  9:26 ` rguenth at gcc dot gnu.org
2023-07-27 10:54 ` redi at gcc dot gnu.org
2023-07-28 10:54 ` arsen at gcc dot gnu.org [this message]
2024-05-21  9:15 ` [Bug libstdc++/109814] [13/14/15 " jakub at gcc dot gnu.org

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=bug-109814-4-D8NdXmkE7Q@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).