Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: <binutils@sourceware.org>, <gcc-patches@gcc.gnu.org>,
	<gdb-patches@sourceware.org>
Subject: Re: [PATCH] Backport gettext fixes to get rid of warnings on macOS
Date: Thu, 06 Sep 2018 10:36:00 -0000	[thread overview]
Message-ID: <2388ae29-d2b9-f7f1-4e8b-44f157ccbcd1@ericsson.com> (raw)
In-Reply-To: <1533135533-16471-1-git-send-email-simon.marchi@ericsson.com>

On 2018-08-01 03:58 PM, Simon Marchi wrote:
> This patch was tested to build binutils-gdb on GNU/Linux and macOS.  It can be
> applied to the gcc repo too, after fixing some trivial merge conflicts (someone
> else will need to do it, as I don't have push access to gcc).  Although I think
> it is relatively low-risk, building gcc on macOS was not tested with this
> patch, so if somebody that has already a macOS build can do it, it would be
> appreciated.
> 
> Two fixes were committed recently to the gettext repo in order to make
> gdb build warning-free on macOS.  This patch backports them both:
> 
>   - Make the format_arg attribute effective also in the case _INTL_REDIRECT_INLINE.
>     113893dce80358a4ae0d9463ce73c5670c81cf0c
>     http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=113893dce80358a4ae0d9463ce73c5670c81cf0c
> 
>   - Enable the format_arg attribute also on clang on Mac OS X.
>     bd6a52241c7c83c90e043ace2082a2508d273f55
>     http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=bd6a52241c7c83c90e043ace2082a2508d273f55
> 
> intl/ChangeLog:
> 
> 	* libgnuintl.h (_INTL_MAY_RETURN_STRING_ARG, gettext, dgettext,
> 	dcgettext, ngettext, dngettext, dcngettext): Backport changes
> 	from upstream gettext.
> ---
>  intl/libgnuintl.h | 35 +++++++++++++++++++++++------------
>  1 file changed, 23 insertions(+), 12 deletions(-)
> 
> diff --git a/intl/libgnuintl.h b/intl/libgnuintl.h
> index acc9093..7616d6f 100644
> --- a/intl/libgnuintl.h
> +++ b/intl/libgnuintl.h
> @@ -115,7 +115,7 @@ extern "C" {
>  /* _INTL_MAY_RETURN_STRING_ARG(n) declares that the given function may return
>     its n-th argument literally.  This enables GCC to warn for example about
>     printf (gettext ("foo %y")).  */
> -#if __GNUC__ >= 3 && !(__APPLE_CC__ > 1 && defined __cplusplus)
> +#if defined __GNUC__ && __GNUC__ >= 3 && !(defined __APPLE_CC__ && __APPLE_CC__ > 1 && !(defined __clang__ && __clang__ && __clang_major__ >= 3) && defined __cplusplus)
>  # define _INTL_MAY_RETURN_STRING_ARG(n) __attribute__ ((__format_arg__ (n)))
>  #else
>  # define _INTL_MAY_RETURN_STRING_ARG(n)
> @@ -127,7 +127,9 @@ extern "C" {
>  #ifdef _INTL_REDIRECT_INLINE
>  extern char *libintl_gettext (const char *__msgid)
>         _INTL_MAY_RETURN_STRING_ARG (1);
> -static inline char *gettext (const char *__msgid)
> +static inline
> +_INTL_MAY_RETURN_STRING_ARG (1)
> +char *gettext (const char *__msgid)
>  {
>    return libintl_gettext (__msgid);
>  }
> @@ -145,7 +147,9 @@ extern char *gettext _INTL_PARAMS ((const char *__msgid))
>  #ifdef _INTL_REDIRECT_INLINE
>  extern char *libintl_dgettext (const char *__domainname, const char *__msgid)
>         _INTL_MAY_RETURN_STRING_ARG (2);
> -static inline char *dgettext (const char *__domainname, const char *__msgid)
> +static inline
> +_INTL_MAY_RETURN_STRING_ARG (2)
> +char *dgettext (const char *__domainname, const char *__msgid)
>  {
>    return libintl_dgettext (__domainname, __msgid);
>  }
> @@ -165,8 +169,9 @@ extern char *dgettext _INTL_PARAMS ((const char *__domainname,
>  extern char *libintl_dcgettext (const char *__domainname, const char *__msgid,
>  				int __category)
>         _INTL_MAY_RETURN_STRING_ARG (2);
> -static inline char *dcgettext (const char *__domainname, const char *__msgid,
> -			       int __category)
> +static inline
> +_INTL_MAY_RETURN_STRING_ARG (2)
> +char *dcgettext (const char *__domainname, const char *__msgid, int __category)
>  {
>    return libintl_dcgettext (__domainname, __msgid, __category);
>  }
> @@ -188,8 +193,10 @@ extern char *dcgettext _INTL_PARAMS ((const char *__domainname,
>  extern char *libintl_ngettext (const char *__msgid1, const char *__msgid2,
>  			       unsigned long int __n)
>         _INTL_MAY_RETURN_STRING_ARG (1) _INTL_MAY_RETURN_STRING_ARG (2);
> -static inline char *ngettext (const char *__msgid1, const char *__msgid2,
> -			      unsigned long int __n)
> +static inline
> +_INTL_MAY_RETURN_STRING_ARG (1) _INTL_MAY_RETURN_STRING_ARG (2)
> +char *ngettext (const char *__msgid1, const char *__msgid2,
> +		unsigned long int __n)
>  {
>    return libintl_ngettext (__msgid1, __msgid2, __n);
>  }
> @@ -210,8 +217,10 @@ extern char *ngettext _INTL_PARAMS ((const char *__msgid1,
>  extern char *libintl_dngettext (const char *__domainname, const char *__msgid1,
>  				const char *__msgid2, unsigned long int __n)
>         _INTL_MAY_RETURN_STRING_ARG (2) _INTL_MAY_RETURN_STRING_ARG (3);
> -static inline char *dngettext (const char *__domainname, const char *__msgid1,
> -			       const char *__msgid2, unsigned long int __n)
> +static inline
> +_INTL_MAY_RETURN_STRING_ARG (2) _INTL_MAY_RETURN_STRING_ARG (3)
> +char *dngettext (const char *__domainname, const char *__msgid1,
> +		 const char *__msgid2, unsigned long int __n)
>  {
>    return libintl_dngettext (__domainname, __msgid1, __msgid2, __n);
>  }
> @@ -234,9 +243,11 @@ extern char *libintl_dcngettext (const char *__domainname,
>  				 const char *__msgid1, const char *__msgid2,
>  				 unsigned long int __n, int __category)
>         _INTL_MAY_RETURN_STRING_ARG (2) _INTL_MAY_RETURN_STRING_ARG (3);
> -static inline char *dcngettext (const char *__domainname,
> -				const char *__msgid1, const char *__msgid2,
> -				unsigned long int __n, int __category)
> +static inline
> +_INTL_MAY_RETURN_STRING_ARG (2) _INTL_MAY_RETURN_STRING_ARG (3)
> +char *dcngettext (const char *__domainname,
> +		  const char *__msgid1, const char *__msgid2,
> +		  unsigned long int __n, int __category)
>  {
>    return libintl_dcngettext (__domainname, __msgid1, __msgid2, __n, __category);
>  }
> 

Could somebody from gcc take a look at and hopefully merge this?

Thanks,

Simon


  parent reply	other threads:[~2018-09-06 10:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 14:59 Simon Marchi
2018-08-01 18:59 ` Simon Marchi
2018-08-02 17:44 ` Tom Tromey
2018-08-02 18:57   ` Simon Marchi
2018-09-06 10:36 ` Simon Marchi [this message]
2018-09-19  4:09   ` 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=2388ae29-d2b9-f7f1-4e8b-44f157ccbcd1@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.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