public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/113278] analyzer tests relying on fileno() fail on arm-eabi Date: Thu, 15 Feb 2024 17:31:33 +0000 [thread overview] Message-ID: <bug-113278-4-EOjKQILcfF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113278-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113278 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Torbjorn Svensson <azoff@gcc.gnu.org>: https://gcc.gnu.org/g:8e8c2d2b34971bb29e74341a3efc625f1db06639 commit r14-9015-g8e8c2d2b34971bb29e74341a3efc625f1db06639 Author: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Date: Thu Feb 15 17:46:24 2024 +0100 testsuite: Define _POSIX_SOURCE for tests [PR113278] As the tests assume that fileno() is visible (only part of POSIX), define the guard to ensure that it's visible. Currently, glibc appears to always have this defined in C++, newlib does not. Without this patch, fails like this can be seen: Testing analyzer/fileno-1.c, -std=c++98 .../fileno-1.c: In function 'int test_pass_through(FILE*)': .../fileno-1.c:5:10: error: 'fileno' was not declared in this scope FAIL: c-c++-common/analyzer/fileno-1.c -std=c++98 (test for excess errors) Patch has been verified on Linux. gcc/testsuite/ChangeLog: PR testsuite/113278 * c-c++-common/analyzer/fileno-1.c: Define _POSIX_SOURCE. * c-c++-common/analyzer/flex-with-call-summaries.c: Same. * c-c++-common/analyzer/flex-without-call-summaries.c: Same. Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
next prev parent reply other threads:[~2024-02-15 17:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-08 17:24 [Bug testsuite/113278] New: " clyon at gcc dot gnu.org 2024-01-08 18:01 ` [Bug testsuite/113278] " rearnsha at gcc dot gnu.org 2024-01-09 3:23 ` pinskia at gcc dot gnu.org 2024-02-15 17:09 ` torbjorn.svensson at foss dot st.com 2024-02-15 17:31 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-19 9:17 ` azoff 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-113278-4-EOjKQILcfF@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: linkBe 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).