[Bug middle-end/49191] gcc.dg/memcpy-3.c FAILs on SPARC

[richard.guenther at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49191

--- Comment #1 from richard.guenther at gmail dot com <richard.guenther at gmail dot com> 2011-05-27 13:53:57 UTC ---
On Fri, May 27, 2011 at 3:50 PM, ro at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49191
>
>           Summary: gcc.dg/memcpy-3.c FAILs on SPARC
>           Product: gcc
>           Version: 4.7.0
>            Status: UNCONFIRMED
>          Severity: normal
>          Priority: P3
>         Component: middle-end
>        AssignedTo: unassigned@gcc.gnu.org
>        ReportedBy: ro@gcc.gnu.org
>                CC: ebotcazou@gcc.gnu.org, richard.guenther@gmail.com
>              Host: sparc-sun-solaris2.*
>            Target: sparc-sun-solaris2.*
>             Build: sparc-sun-solaris2.*
>
>
> The new gcc.dg/memcpy-3.c test FAILs on Solaris/SPARC:
>
> FAIL: gcc.dg/memcpy-3.c scan-tree-dump-not optimized "memcpy"
> FAIL: gcc.dg/memcpy-3.c scan-tree-dump-times optimized "MEM" 1
>
> The dump looks like this:
>
> ;; Function get_int (get_int)
>
> get_int (const void * p)
> {
>  int w;
>  int D.1980;
>
> <bb 2>:
>  __builtin_memcpy (&w, p_1(D), 4);
>  D.1980_2 = w;
>  return D.1980_2;

Is sparc a strict-alignment target?  Then that's expected.

Hmm.  Not sure we have a dg-effective-target strict-align ...
so you probably have to add some xfails.