public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgcc: Avoid -Wbuiltin-declaration-mismatch warnings in emutls.c
Date: Wed, 6 Dec 2023 11:25:10 +0100 (CET)	[thread overview]
Message-ID: <nrs41q26-34sp-9821-q1q5-n06q287312s0@fhfr.qr> (raw)
In-Reply-To: <ZXBHF0Qggxkoz/ej@tucnak>

On Wed, 6 Dec 2023, Jakub Jelinek wrote:

> Hi!
> 
> 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.
> 
> Tested on x86_64-linux with --disable-tls, ok for trunk?

Works for me.

Richard.

> 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.
> 
> --- libgcc/emutls.c.jj	2023-01-16 11:52:16.780723793 +0100
> +++ libgcc/emutls.c	2023-12-06 10:49:46.438060090 +0100
> @@ -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
> 
> 	Jakub
> 
> 

-- 
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)

  reply	other threads:[~2023-12-06 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 10:04 Jakub Jelinek
2023-12-06 10:25 ` Richard Biener [this message]
2023-12-06 17:48 ` Jeff Law

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=nrs41q26-34sp-9821-q1q5-n06q287312s0@fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).