public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/98076] Increase speed of integer I/O Date: Mon, 27 Dec 2021 20:13:52 +0000 [thread overview] Message-ID: <bug-98076-4-hyYPl09gqZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98076-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98076 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ro at gcc dot gnu.org --- Comment #10 from Rainer Orth <ro at gcc dot gnu.org> --- This patch broke (at least) Solaris bootstrap: /vol/gcc/src/hg/master/local/libgfortran/runtime/string.c: In function 'gfc_itoa': /vol/gcc/src/hg/master/local/libgfortran/runtime/string.c:245:73: error: macro "static_assert" requires 2 arguments, but only 1 given 245 | static_assert(sizeof(GFC_UINTEGER_LARGEST) <= 2 * sizeof(uint64_t)); | ^ In file included from /vol/gcc/src/hg/master/local/libgfortran/runtime/string.c:26: /usr/include/assert.h:25: note: macro "static_assert" defined here 25 | #define static_assert(a, b) _Static_assert(a, b) | /vol/gcc/src/hg/master/local/libgfortran/runtime/string.c:245:7: error: 'static_assert' undeclared (first use in this function) 245 | static_assert(sizeof(GFC_UINTEGER_LARGEST) <= 2 * sizeof(uint64_t)); | ^~~~~~~~~~~~~ /vol/gcc/src/hg/master/local/libgfortran/runtime/string.c:245:7: note: each undeclared identifier is reported only once for each function it appears in make[6]: *** [Makefile:2765: string.lo] Error 1 According to https://en.cppreference.com/w/c/language/_Static_assert, the one-arg form of _Static_assert/static_assert is new since C23, while Solaris <assert.h> only supports the two-arg form.
next prev parent reply other threads:[~2021-12-27 20:13 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-01 6:49 [Bug libfortran/98076] New: " tkoenig at gcc dot gnu.org 2020-12-01 6:50 ` [Bug libfortran/98076] " tkoenig at gcc dot gnu.org 2021-04-16 16:22 ` tkoenig at gcc dot gnu.org 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2021-07-29 19:18 ` anlauf at gcc dot gnu.org 2021-12-16 21:31 ` fxcoudert at gcc dot gnu.org 2021-12-16 21:40 ` fxcoudert at gcc dot gnu.org 2021-12-16 23:20 ` fxcoudert at gcc dot gnu.org 2021-12-17 9:05 ` fxcoudert at gcc dot gnu.org 2021-12-25 13:04 ` fxcoudert at gcc dot gnu.org 2021-12-26 11:14 ` fxcoudert at gcc dot gnu.org 2021-12-27 20:13 ` ro at gcc dot gnu.org [this message] 2021-12-27 20:25 ` fxcoudert at gcc dot gnu.org 2021-12-27 21:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-98076-4-hyYPl09gqZ@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).