public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r14-6218] libgcc: Avoid -Wbuiltin-declaration-mismatch warnings in emutls.c
@ 2023-12-06 11:27 Jakub Jelinek
  0 siblings, 0 replies; only message in thread
From: Jakub Jelinek @ 2023-12-06 11:27 UTC (permalink / raw)
  To: gcc-cvs

https://gcc.gnu.org/g:d7ceffab96ecd021d3e869dff33d0ad4b8577c4f

commit r14-6218-gd7ceffab96ecd021d3e869dff33d0ad4b8577c4f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Dec 6 12:27:12 2023 +0100

    libgcc: Avoid -Wbuiltin-declaration-mismatch warnings in emutls.c
    
    When libgcc is being built in --disable-tls configuration or on
    a target without native TLS support, one gets annoying warnings:
    ../../../../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 *);
          |       ^~~~~~~~~~~~~~~~~~~~
    ../../../../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 *);
          |      ^~~~~~~~~~~~~~~~~~~~~~~~
    ../../../../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)
          | ^~~~~~~~~~~~~~~~~~~~
    ../../../../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 thing is that in that case __emutls_get_address and
    __emutls_register_common are builtins, and are declared with void *
    arguments rather than struct __emutls_object *.
    Now, struct __emutls_object is a type private to libgcc/emutls.c and the
    middle-end creates on demand when calling the builtins a similar structure
    (with small differences, like not having the union in there).
    
    We have a precedent for this e.g. for fprintf or strftime builtins where
    the builtins are created with magic fileptr_type_node or const_tm_ptr_type_node
    types and then match it with user definition of pointers to some structure,
    but I think for this case users should never define these functions
    themselves nor call them and having special types for them in the compiler
    would mean extra compile time spent during compiler initialization and more
    GC data, so I think it is better to keep the compiler as is.
    
    On the library side, there is an option to just follow what the
    compiler is doing and do
     EMUTLS_ATTR void
    -__emutls_register_common (struct __emutls_object *obj,
    +__emutls_register_common (void *xobj,
                               word size, word align, void *templ)
     {
    +  struct __emutls_object *obj = (struct __emutls_object *) xobj;
    but that will make e.g. libabigail complain about ABI change in libgcc.
    
    So, the patch just turns the warning off.
    
    2023-12-06  Thomas Schwinge  <thomas@codesourcery.com>
                Jakub Jelinek  <jakub@redhat.com>
    
            PR libgcc/109289
            * emutls.c: Add GCC diagnostic ignored "-Wbuiltin-declaration-mismatch"
            pragma.

Diff:
---
 libgcc/emutls.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/libgcc/emutls.c b/libgcc/emutls.c
index 0fea1f10bfa..95aaed74341 100644
--- a/libgcc/emutls.c
+++ b/libgcc/emutls.c
@@ -57,6 +57,14 @@ struct __emutls_array
 #  define EMUTLS_ATTR
 #endif
 
+/* __emutls_get_address and __emutls_register_common are registered as
+   builtins, but the compiler struct __emutls_object doesn't have
+   a union in there and is only created when actually needed for
+   the calls to the builtins, so the builtins are created with void *
+   arguments rather than struct __emutls_object *.  Avoid
+   -Wbuiltin-declaration-mismatch warnings.  */
+#pragma GCC diagnostic ignored "-Wbuiltin-declaration-mismatch"
+
 EMUTLS_ATTR
 void *__emutls_get_address (struct __emutls_object *);
 EMUTLS_ATTR

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-12-06 11:27 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-06 11:27 [gcc r14-6218] libgcc: Avoid -Wbuiltin-declaration-mismatch warnings in emutls.c Jakub Jelinek

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).