From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Newlib <newlib@sourceware.org>
Cc: Yvan Roux <yvan.roux@foss.st.com>
Subject: Mismatch between newlib and glibc regarding fileno
Date: Fri, 9 Feb 2024 17:29:56 +0100 [thread overview]
Message-ID: <52858367-f116-413e-b107-61c8afce156b@foss.st.com> (raw)
Hi all,
I've been trying to run tests for arm-none-eabi on GCC14 tree.
What I've seen is that fileno() is not available. If you look though the
header files, I see that this is guarded by __POSIX_VISIBLE and due to a
recent change in the GCC testsuite (part of PR96395), they moved the
test case to gcc/testsuite/c-c++-common/analyzer/fileno-1.c and then
invoke it with g++ and -std=c++98. With this change, strict ANSI is
defined, but not __POSIX_VISIBLE.
If I run the same test on the native g++ tool in Ubuntu, I instead get
that __USE_POSIX is set (the guard for fileno() in glibc), so this
differs from the behavior noticed with newlib.
Is it correct that newlib does not define __POSIX_VISIBLE when g++ is
invoked with -std=c++98 (or any other standard that does not use the GNU
extensions)?
It can also be seen using gcc with -std=c11 for example, so it's not
strictly a C vs C++ issue.
The expression used in glibc:
https://github.com/bminor/glibc/blob/master/include/features.h#L335
The expression used in newlib:
https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/include/sys/features.h;h=6a925c87e9ec333fc51538201aa7b52d24b3ca5b;hb=refs/heads/main#l148
Kind regards,
Torbjörn
next reply other threads:[~2024-02-09 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 16:29 Torbjorn SVENSSON [this message]
2024-02-09 16:40 ` Andrew Pinski
2024-02-09 16:54 ` Corinna Vinschen
2024-02-12 15:36 ` Torbjorn SVENSSON
2024-02-12 16:33 ` Corinna Vinschen
2024-02-12 16:40 ` Corinna Vinschen
2024-02-12 17:11 ` Torbjorn SVENSSON
2024-02-12 17:44 ` Corinna Vinschen
2024-02-12 18:14 ` Joseph Myers
2024-02-12 19:27 ` Torbjorn SVENSSON
2024-02-12 19:40 ` Corinna Vinschen
2024-02-15 17:36 ` Torbjorn SVENSSON
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=52858367-f116-413e-b107-61c8afce156b@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=newlib@sourceware.org \
--cc=yvan.roux@foss.st.com \
/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).