public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111639] HAVE_ACOSF etc. are wrong on avr
Date: Sat, 30 Sep 2023 19:16:33 +0000	[thread overview]
Message-ID: <bug-111639-4-yhpr3Ilmi2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111639-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> The <math.h> in avr-libc does things like this:
> 
> extern double acos(double __x) __ATTR_CONST__;
> #define acosf	acos		/**< The alias for acos().	*/

This is no more the case with current AVR-LibC, which uses proper prototypes
and symbols for acos, acosf and acosl etc.

Here is math.h from the AVR-LibC v2.1 release (Jan 2022) :
https://github.com/avrdudes/avr-libc/blob/c466ef11ebf6cf774b7148dbd78c250789989ce0/include/math.h
(which has only acos and acosf, where the alias is implemented using assembly
name __asm("")).

The next release will also include long double prototypes, and they are proper
prototypes (without __asm("") names).

math.h from current HEAD:
https://github.com/avrdudes/avr-libc/blob/main/include/math.h

  parent reply	other threads:[~2023-09-30 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 13:35 [Bug libstdc++/111639] New: " redi at gcc dot gnu.org
2023-09-29 14:07 ` [Bug libstdc++/111639] " redi at gcc dot gnu.org
2023-09-30 19:16 ` gjl at gcc dot gnu.org [this message]
2023-09-30 19:21 ` redi at gcc dot gnu.org
2023-10-01  8:17 ` gjl at gcc dot gnu.org
2023-10-01  8:37 ` redi at gcc dot gnu.org
2023-10-01 16:54 ` gjl at gcc dot gnu.org
2023-10-01 19:04 ` redi at gcc dot gnu.org
2023-10-01 19:05 ` redi at gcc dot gnu.org
2024-06-15 13:28 ` gjl 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-111639-4-yhpr3Ilmi2@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).