Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gcc-4.5: added thumb2 build patch
Date: Mon, 07 Feb 2011 17:35:55 +0100	[thread overview]
Message-ID: <iip71b$7tv$1@dough.gmane.org> (raw)
In-Reply-To: <1297093986-24331-2-git-send-email-enrico.scholz@sigma-chemnitz.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07-02-11 16:53, Enrico Scholz wrote:
> Fix for http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43999 and is
> required to build gcc for Thumb2 only architectures (e.g. Cortex-M3).
> 
> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> ---
>  recipes/gcc/gcc-4.5.inc                |    3 ++-
>  recipes/gcc/gcc-4.5/thumb2-build.patch |   11 +++++++++++
>  2 files changed, 13 insertions(+), 1 deletions(-)
>  create mode 100644 recipes/gcc/gcc-4.5/thumb2-build.patch
> 
> diff --git a/recipes/gcc/gcc-4.5.inc b/recipes/gcc/gcc-4.5.inc
> index b630528..9ba2e22 100644
> --- a/recipes/gcc/gcc-4.5.inc
> +++ b/recipes/gcc/gcc-4.5.inc
> @@ -8,7 +8,7 @@ DEPENDS = "mpfr gmp libmpc libelf"
>  NATIVEDEPS = "mpfr-native gmp-native libmpc-native"
>  
>  
> -INC_PR = "r31"
> +INC_PR = "r32"
>  
>  SRCREV = "168622"
>  PV = "4.5"
> @@ -166,6 +166,7 @@ SRC_URI = "svn://gcc.gnu.org/svn/gcc/branches;module=${BRANCH} \
>  #	   file://linaro/gcc-4.5-linaro-r99457.patch \
>  	   file://gcc-scalar-widening-pr45847.patch \
>  	   file://gcc-arm-volatile-bitfield-fix.patch \
> +	   file://thumb2-build.patch \
>  	  "
>  
>  SRC_URI_append_mips64 = " file://mips64-nomultilib.patch "
> diff --git a/recipes/gcc/gcc-4.5/thumb2-build.patch b/recipes/gcc/gcc-4.5/thumb2-build.patch
> new file mode 100644
> index 0000000..8fefbfa
> --- /dev/null
> +++ b/recipes/gcc/gcc-4.5/thumb2-build.patch
> @@ -0,0 +1,11 @@
> +Index: gcc/config/arm/lib1funcs.asm
> +===================================================================
> +--- a/gcc/config/arm/lib1funcs.asm	(revision 163231)
> ++++ b/gcc/config/arm/lib1funcs.asm	(working copy)
> +@@ -642,5 +642,5 @@
> + 	cmp	\dividend, #0			@ Early termination?
> +-	do_it	hs, t
> ++	do_it	ne, t
> + 	movnes	\curbit,   \curbit,  lsr #4	@ No, any more bits to do?
> + 	movne	\divisor,  \divisor, lsr #4
> + 	bne	1b

COuld you please add some more information to the thumb2-build.patch
file? The author and bugzilla link should be enough.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNUB9rMkyGM64RGpERArtIAJsGlpCCEoVhxGVTNKyUAc1tFak9tACeJuvO
4aiwFXOVPWtxIRXxQfTsXFg=
=hrQn
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-02-07 16:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 15:53 [PATCH] cortex-m3: adjusted target cflags Enrico Scholz
2011-02-07 15:53 ` [PATCH] gcc-4.5: added thumb2 build patch Enrico Scholz
2011-02-07 16:35   ` Koen Kooi [this message]
2011-02-07 17:25   ` [PATCH, v2] " Enrico Scholz
2011-02-07 18:30     ` Khem Raj
2011-02-07 19:33 ` [PATCH] cortex-m3: adjusted target cflags Khem Raj
2011-02-07 19:39   ` Mark Hatle
2011-02-07 20:19     ` Khem Raj
2011-02-07 20:42       ` Mark Hatle
2011-02-07 20:59   ` Enrico Scholz
2011-02-07 21:35     ` Khem Raj
2011-02-07 22:27       ` Enrico Scholz
2011-02-07 22:35         ` Khem Raj

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='iip71b$7tv$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.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