obtained gcc-4.6.4.tar.bz2 from upstream website;upstream

verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.

downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.

if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.

1 files changed, 42 insertions, 0 deletions

diff --git a/gcc/testsuite/gcc.dg/vmx/gcc-bug-i.c b/gcc/testsuite/gcc.dg/vmx/gcc-bug-i.c
new file mode 100644
index 000000000..58ccb3fe7
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/vmx/gcc-bug-i.c
@@ -0,0 +1,42 @@
+#include "harness.h"
+
+/* This problem occurs if a function is inlined.  When its local
+   variables get allocated space on the caller's (the function to
+   which it is inlined) stack frame, they don't get 16-byte alignment
+   even if they need it.  Here's an example with a union (that's the
+   first case I uncovered, but it's probably a general occurrence on
+   inlining).  */
+
+#define N 10
+/* adjust N = size of buffer to try to get bad alignment for inlined union */
+
+#define DO_INLINE __attribute__ ((always_inline))
+#define DONT_INLINE __attribute__ ((noinline))
+
+static DO_INLINE int inline_me(vector signed short data) 
+{
+  union {vector signed short v; signed short s[8];} u;
+  u.v = data;
+  return u.s[7];
+}
+
+static DONT_INLINE int foo(vector signed short data)
+{
+  int c, buffer[N], i;
+  c = inline_me(data);
+  for (i=0; i<N; i++) {
+    if (i == 0)
+      buffer[i] = c;
+    else
+      buffer[i] = buffer[i-1] + c*i;
+  }
+  return buffer[N-1];
+}
+
+static void test()
+{
+  check(foo((vector signed short)
+	    ((vector unsigned char){1,2,3,4,5,6,7,8,
+				   9,10,11,12,13,14,15,16})) == 0x2b4e0,
+	"foo");
+}