On 12/5/06, Andrew MacLeod <[EMAIL PROTECTED]> wrote:
My preference is to check in the TER code which exposes this bug, and
open a PR against the failure with this info. That way we don't lose
track of the problem, and someone can fix it at their leisure. Until
then there will be a testsuite fai
>
>
> I've been investigating a testsuite failure which shows up with the new
> TER implementation, and it appears to be a bug in the code for
> expand_builtin_memcpy.
>
> Does that seem reasonable? or would everyone prefer I get it fixed
> before checking in the TER code?
I would prefer you
I've been investigating a testsuite failure which shows up with the new
TER implementation, and it appears to be a bug in the code for
expand_builtin_memcpy.
The problem is an array slice of a string constant, which is this case
originates in gfortran.
The source code looks like:
subroutine f
