On Linux/x86-64, revision 163191 gave FAIL: gfortran.dg/array_memcpy_3.f90 -O scan-tree-dump-times original "memcpy|(ref-all.*ref-all)" 2 FAIL: gfortran.dg/array_memcpy_3.f90 -O scan-tree-dump-times original "memcpy|(ref-all.*ref-all)" 2 Revision 163187 is OK. This may be caused by revision 163189: http://gcc.gnu.org/ml/gcc-cvs/2010-08/msg00400.html Linux/ia32 doesn't have this regression.
The pattern doesn't match even though I see two memcpy calls!?
(In reply to comment #1) > The pattern doesn't match even though I see two memcpy calls!? > I am using # make RUNTESTFLAGS="--target_board 'unix{-m32,}'" check 2 failures are 1 for 64bit and 1 for 32bit.
I see the fails, but the pattern should still match.
I was wrong. Linux/ia32 has the same regression: FAIL: gfortran.dg/array_memcpy_3.f90 -O scan-tree-dump-times original "memcpy|(ref-all.*ref-all)" 2
Pls don't change back bug attributes all the time...
*** Bug 45275 has been marked as a duplicate of this bug. ***
Does "memcpy|(ref-all.*ref-all)" need to be "(memcpy|(ref-all.*ref-all))" or perhaps "(memcpy|ref-all.*ref-all)". Everyplace else I see a | in a scan statement there are parentheses around the options.
! { dg-final { scan-tree-dump-times "memcpy|ref-all.*ref-all" 2 "original" } } worked for me on IA64 where we have 2 memcpys' in the output. Neither of my suggestions from comment #7 worked. I don't know if this will work on a platform which generates the 'ref-all' strings instead of memcpy's. All my platforms; IA64, PA, x86 seem to generate memcpy.
Subject: Bug 45266 Author: rguenth Date: Tue Aug 17 09:47:44 2010 New Revision: 163297 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=163297 Log: 2010-08-17 Richard Guenther <rguenther@suse.de> PR testsuite/45266 * gfortran.dg/array_memcpy_3.f90: Adjust pattern. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/array_memcpy_3.f90
Fixed then.