public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Renlin Li <Renlin.Li@arm.com>,
	 "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: Re: PATCH][ARM][4.8]Backport "Fix definition of __ARM_SIZEOF_WCHAR_T"
Date: Tue, 13 Jan 2015 16:00:00 -0000	[thread overview]
Message-ID: <54B53FCB.2070102@arm.com> (raw)
In-Reply-To: <54B53F7C.5000902@arm.com>

On 13/01/15 15:53, Renlin Li wrote:
> Hi all,
> 
> This is a backport patch for 
> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=213864
> 
> arm-none-eabi regression test has been done, no new issues.
> Okay for branch 4.8?
> 
> gcc/ChangeLog
> Fix PR target/61413
> Backport from mainline.
> 
> 2014-08-12 Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
> 
>      PR target/61413
>      * config/arm/arm.h (TARGET_CPU_CPP_BUILTINS): Fix definition
>      of __ARM_SIZEOF_WCHAR_T.
> 
> 
> 
> backport.patch
> 
> 
> diff --git a/gcc/config/arm/arm.h b/gcc/config/arm/arm.h
> index c0f2184..23333eb 100644
> --- a/gcc/config/arm/arm.h
> +++ b/gcc/config/arm/arm.h
> @@ -74,8 +74,8 @@ extern char arm_arch_name[];
>  	builtin_define_with_int_value (				\
>  	  "__ARM_SIZEOF_MINIMAL_ENUM",				\
>  	  flag_short_enums ? 1 : 4);				\
> -	builtin_define_with_int_value (				\
> -	  "__ARM_SIZEOF_WCHAR_T", WCHAR_TYPE_SIZE);		\
> +	builtin_define_type_sizeof ("__ARM_SIZEOF_WCHAR_T",	\
> +				    wchar_type_node);		\
>  	if (TARGET_ARM_ARCH_PROFILE)				\
>  	  builtin_define_with_int_value (			\
>  	    "__ARM_ARCH_PROFILE", TARGET_ARM_ARCH_PROFILE);	\
> 

OK.


      reply	other threads:[~2015-01-13 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 15:58 Renlin Li
2015-01-13 16:00 ` Richard Earnshaw [this message]

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=54B53FCB.2070102@arm.com \
    --to=rearnsha@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Renlin.Li@arm.com \
    --cc=gcc-patches@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).