This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What's up with g++.dg/ext/mv*.C?
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Paolo Carlini <paolo dot carlini at oracle dot com>
- Cc: gcc at gnu dot org, tmsriram at google dot com
- Date: Thu, 13 Jun 2013 19:09:47 +0200
- Subject: Re: What's up with g++.dg/ext/mv*.C?
- References: <51B99EB2 dot 5060602 at oracle dot com> <51B9A085 dot 9060004 at oracle dot com> <51B9A137 dot 2090308 at oracle dot com>
> On 06/13/2013 12:35 PM, Paolo Carlini wrote:
> >On 06/13/2013 12:28 PM, Paolo Carlini wrote:
> >>Hi,
> >>
> >>these FAILs are much more recent but frankly I'm also puzzled:
> >>is a fix actively in the making? Do we have any sort of time for
> >>that?
> >This is PR57548 and a patch is approved but unapplied:
> >
> > http://gcc.gnu.org/ml/gcc-patches/2013-06/msg00426.html
> >
> >I'll do that myself ASAP if nobody beats me.
> In fact the patch is already in but the regressions are still there, eg:
>
> http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg01257.html
>
> Is it actually a different issue or what?
I looked into it and it is caused at least the mv1 is caused by loop preserving code.
tree-inline expects loops to be build (and by Richard it should be the case) but
they are not. I did not work out yet why it is the case, if time allows I iwll try
to look into it tonight or tomorrow.
Honza
>
> Paolo.