public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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: Sat, 02 Dec 2023 23:00:31 +0000 [thread overview]
Message-ID: <bug-109289-4-MKG2FrkZso@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
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu.org
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #4)
> What I can I do here to help? What's an easy emutls target to build?
--disable-tls is enough to get the warning while building libgcc on
x86_64-linux-gnu:
/home/apinski/src/upstream-gcc-match/gcc/libgcc/emutls.c:61:7: warning:
conflicting types for built-in function ‘__emutls_get_address’; expected ‘void
*(void *)’ [-Wbuiltin-declaration-mismatch]
61 | void *__emutls_get_address (struct __emutls_object *);
| ^~~~~~~~~~~~~~~~~~~~
/home/apinski/src/upstream-gcc-match/gcc/libgcc/emutls.c:63:6: warning:
conflicting types for built-in function ‘__emutls_register_common’; expected
‘void(void *, unsigned int, unsigned int, void *)’
[-Wbuiltin-declaration-mismatch]
63 | void __emutls_register_common (struct __emutls_object *, word, word,
void *);
| ^~~~~~~~~~~~~~~~~~~~~~~~
/home/apinski/src/upstream-gcc-match/gcc/libgcc/emutls.c:140:1: warning:
conflicting types for built-in function ‘__emutls_get_address’; expected ‘void
*(void *)’ [-Wbuiltin-declaration-mismatch]
140 | __emutls_get_address (struct __emutls_object *obj)
| ^~~~~~~~~~~~~~~~~~~~
/home/apinski/src/upstream-gcc-match/gcc/libgcc/emutls.c:204:1: warning:
conflicting types for built-in function ‘__emutls_register_common’; expected
‘void(void *, unsigned int, unsigned int, void *)’
[-Wbuiltin-declaration-mismatch]
204 | __emutls_register_common (struct __emutls_object *obj,
| ^~~~~~~~~~~~~~~~~~~~~~~~
The build does not fail.
next prev parent reply other threads:[~2023-12-02 23:00 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 [this message]
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
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-MKG2FrkZso@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).