> I think it is worthwhile, various targets have many different ways to expand
> memcpy, admittedly i?86/x86_64 probably the biggest number of these, and
> while right now you've encountered it on ia32 with certain options doesn't
> mean that in a few years it couldn't hit some unrelated target, arm, sh,
> sparc, whatever.
Ok, that makes sense.
I've never written torture tests before, could you please check if I did it
right?

Changelog:
gcc:
2013-09-09  Michael Zolotukhin  <michael.v.zolotukhin@gmail.com>

	* config/i386/i386.c (ix86_expand_movmem): Fix epilogue generation.

gcc/testsuite:
2013-09-09  Michael Zolotukhin  <michael.v.zolotukhin@gmail.com>

	* gcc.c-torture/execute/memcpy-3.c: New test.
	* gcc.c-torture/execute/memcpy-3.x: New file.


Michael
> 	Jakub