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

diff --git a/gcc/testsuite/gfortran.dg/mvbits_1.f90 b/gcc/testsuite/gfortran.dg/mvbits_1.f90
new file mode 100644
index 000000000..90e92bb0e
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/mvbits_1.f90
@@ -0,0 +1,39 @@
+! PR 25577
+! MVBITS didn't work correctly for integer types wider than a C int
+! The testcase is based on the one Dale Ranta posted in the bug report
+implicit none
+integer(1) i1,j1
+integer(2) i2,j2
+integer(4) i4,j4
+integer(8) i8,j8
+integer ibits,n
+
+ibits=bit_size(1_1)
+do n=1,ibits
+   i1=-1
+   call mvbits(1_1, 0,n,i1,0)
+   j1=-1-2_1**n+2
+   if(i1.ne.j1)call abort
+enddo
+ibits=bit_size(1_2)
+do n=1,ibits
+   i2=-1
+   call mvbits(1_2, 0,n,i2,0)
+   j2=-1-2_2**n+2
+   if(i2.ne.j2)call abort
+enddo
+ibits=bit_size(1_4)
+do n=1,ibits
+   i4=-1
+   call mvbits(1_4, 0,n,i4,0)
+   j4=-1-2_4**n+2
+   if(i4.ne.j4)call abort
+enddo
+ibits=bit_size(1_8)
+do n=1,ibits
+   i8=-1
+   call mvbits(1_8, 0,n,i8,0)
+   j8=-1-2_8**n+2
+   if(i8.ne.j8)call abort
+enddo
+end