public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/109289] Conflicting types for built-in functions in libgcc/emutls.c Date: Wed, 06 Dec 2023 11:03:14 +0000 [thread overview] Message-ID: <bug-109289-4-wi3aTsRzFR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109289-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289 Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #8 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to myself from comment #2) > [...]/source-gcc/libgcc/emutls.c: In function ‘__emutls_get_address’: > [...]/source-gcc/libgcc/emutls.c:172:13: error: implicit declaration of > function ‘calloc’ [-Wimplicit-function-declaration] > 172 | arr = calloc (size + 1, sizeof (void *)); > | ^~~~~~ > [...]/source-gcc/libgcc/emutls.c:32:1: note: include ‘<stdlib.h>’ or > provide a declaration of ‘calloc’ > 31 | #include "gthr.h" > +++ |+#include <stdlib.h> > 32 | > [...]/source-gcc/libgcc/emutls.c:172:13: warning: incompatible implicit > declaration of built-in function ‘calloc’ [-Wbuiltin-declaration-mismatch] > 172 | arr = calloc (size + 1, sizeof (void *)); > | ^~~~~~ > [...]/source-gcc/libgcc/emutls.c:172:13: note: include ‘<stdlib.h>’ or > provide a declaration of ‘calloc’ > [...]/source-gcc/libgcc/emutls.c:184:13: error: implicit declaration of > function ‘realloc’ [-Wimplicit-function-declaration] > 184 | arr = realloc (arr, (size + 1) * sizeof (void *)); > | ^~~~~~~ > [...]/source-gcc/libgcc/emutls.c:184:13: note: include ‘<stdlib.h>’ or > provide a declaration of ‘realloc’ > [...]/source-gcc/libgcc/emutls.c:184:13: warning: incompatible implicit > declaration of built-in function ‘realloc’ [-Wbuiltin-declaration-mismatch] > [...]/source-gcc/libgcc/emutls.c:184:13: note: include ‘<stdlib.h>’ or > provide a declaration of ‘realloc’ > GCC's suggestion to "include ‘<stdlib.h>’" needs to be carefully reviewed, > in case this is meant to be buildable in an environment without C library > headers? (In reply to Florian Weimer from comment #3) > Thomas, the safe thing to do would be to use __builtin_calloc and > __builtin_realloc in those spots because it avoids a dependency on an > external header that might not exist at this point. That part got resolved differently, in commit r14-6207-g6e84dafcc72d1cd6d028b42f1801e092a91d3214 "tsystem.h: Declare calloc/realloc #ifdef inhibit_libc".
next prev parent reply other threads:[~2023-12-06 11:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-26 22:58 [Bug libgcc/109289] New: " jdx at o2 dot pl 2023-03-27 0:14 ` [Bug libgcc/109289] " pinskia at gcc dot gnu.org 2023-12-01 9:53 ` tschwinge at gcc dot gnu.org 2023-12-01 10:17 ` fw at gcc dot gnu.org 2023-12-02 12:24 ` fw at gcc dot gnu.org 2023-12-02 23:00 ` pinskia at gcc dot gnu.org 2023-12-03 4:09 ` jdx at o2 dot pl 2023-12-05 16:41 ` tschwinge at gcc dot gnu.org 2023-12-06 11:03 ` tschwinge at gcc dot gnu.org [this message] 2023-12-06 11:27 ` cvs-commit at gcc dot gnu.org 2023-12-06 12:53 ` tschwinge 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-109289-4-wi3aTsRzFR@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).