thumb2.md (*thumb2_ior_scc_strict_it): Convert to
> define_insn_and_split. Ensure operands[1] and operands[0] do not
> get assigned the same register.
>
> 2016-01-21 Kyrylo Tkachov
>
> PR target/69403
> * gcc.c-torture/execute/pr69403.c: New test.
--
Han Shen | Software Engineer | shen...@google.com | +1-650-440-3330
Backport trunk:r232727 fix for PR/69403 - wrong
thumb2_ior_scc_strict_it insn pattern.
Note this only affect armv7-a tuned for armv8 arch, tested / booted
affected ChromeOS book.
Ok for google/gcc-4_9 branch?
--
Han Shen
Index: gcc/ChangeLog
ions. But I regard this not an issue ---
at the programming level, there is no way to get one's hand on the
address of a returned structure ---
struct Node foo();
struct Node *p = &foo(); // compiler error - lvalue required as
unary '&' o
2011-11-15 Han Shen
* gcc/Makefile.in:
* gcc/configure:
* gcc/cppdefault.c:
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index ae4f4da..0a05783 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -615,6 +615,7 @@ gcc_tooldir = @gcc_tooldir@
build_tooldir
Hi, this patch provides a new stack protection option -
"fstack-protector-strong".
Background - some times stack-protector is too-simple while stack-protector-all
over-kills, for example, to build one of our core systems, we forcibly add
"-fstack-protector-all" to all compile commands, which br
