From: Pascal Bach <pascal.bach@siemens.com>
To: openembedded-core@lists.openembedded.org
Subject: [krogoth][PATCH] gcc, qemuppc: Explicitly disable forcing SPE flags for 4.9
Date: Fri, 15 Jul 2016 15:22:21 +0200 [thread overview]
Message-ID: <1468588941-2574-1-git-send-email-pascal.bach@siemens.com> (raw)
This ports the missing changes from commit: 7a51776a830167e43cbd185505f62f328704e271
from 5.3 to 4.9 so that qemuppc can be compiled.
Signed-off-by: Pascal Bach <pascal.bach@siemens.com>
---
...Enable-SPE-AltiVec-generation-on-powepc-linux-target.patch | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/meta/recipes-devtools/gcc/gcc-4.9/0049-Enable-SPE-AltiVec-generation-on-powepc-linux-target.patch b/meta/recipes-devtools/gcc/gcc-4.9/0049-Enable-SPE-AltiVec-generation-on-powepc-linux-target.patch
index b98f8ff..77fa18a 100644
--- a/meta/recipes-devtools/gcc/gcc-4.9/0049-Enable-SPE-AltiVec-generation-on-powepc-linux-target.patch
+++ b/meta/recipes-devtools/gcc/gcc-4.9/0049-Enable-SPE-AltiVec-generation-on-powepc-linux-target.patch
@@ -37,6 +37,17 @@ index cb7a94e..d392c2b 100644
extra_options="${extra_options} rs6000/sysv4.opt"
tmake_file="rs6000/t-fprules rs6000/t-ppcos ${tmake_file} rs6000/t-ppccomm"
case ${target} in
+Index: gcc-4.9.3/gcc/config/rs6000/linuxspe.h
+===================================================================
+--- gcc-4.9.3.orig/gcc/config/rs6000/linuxspe.h
++++ gcc-4.9.3/gcc/config/rs6000/linuxspe.h
+@@ -27,6 +27,3 @@
+ #undef TARGET_DEFAULT
+ #define TARGET_DEFAULT MASK_STRICT_ALIGN
+ #endif
+-
+-#undef ASM_DEFAULT_SPEC
+-#define ASM_DEFAULT_SPEC "-mppc -mspe -me500"
--
1.7.9.5
--
2.1.4
next reply other threads:[~2016-07-15 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 13:22 Pascal Bach [this message]
2016-07-15 14:20 ` [krogoth][PATCH] gcc, qemuppc: Explicitly disable forcing SPE flags for 4.9 akuster808
2016-07-15 14:43 ` Pascal Bach
2016-08-04 7:48 ` Pascal Bach
2016-08-15 20:58 ` akuster808
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=1468588941-2574-1-git-send-email-pascal.bach@siemens.com \
--to=pascal.bach@siemens.com \
--cc=openembedded-core@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