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, 31 insertions, 0 deletions

diff --git a/gcc/testsuite/gcc.c-torture/compile/20000825-1.c b/gcc/testsuite/gcc.c-torture/compile/20000825-1.c
new file mode 100644
index 000000000..3c2e5bda7
--- /dev/null
+++ b/gcc/testsuite/gcc.c-torture/compile/20000825-1.c
@@ -0,0 +1,31 @@
+typedef signed int      s32;
+typedef signed long     s64;
+typedef unsigned int    u32;
+typedef unsigned long   u64;
+
+extern __inline__ u32 foobar(int logmask)
+{
+        u32 ret = ~(1 << logmask);      // fails
+        // s32 ret = ~(1 << logmask);   // ok
+        // u64 ret = ~(1 << logmask);   // ok
+        // s64 ret = ~(1 << logmask);   // ok
+        return ret;
+}
+
+// This procedure compiles fine...
+u32 good(u32 var)
+{
+        var = foobar(0);
+        return var;
+}
+
+// This procedure does not compile...
+// Same as above, but formal parameter is a pointer
+// Both good() and fails() compile ok if we choose
+// a different type for "ret" in foobar().
+u32 fails(u32 *var)
+{
+        *var = foobar(0);
+        return *var;
+}
+