[Bug fortran/31867] function result with character LEN computed at run time

2007-05-21 Thread pault at gcc dot gnu dot org
--- Comment #11 from pault at gcc dot gnu dot org 2007-05-21 14:16 --- Subject: Bug 31867 Author: pault Date: Mon May 21 13:16:06 2007 New Revision: 124903 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124903 Log: 2007-05-21 Paul Thomas <[EMAIL PROTECTED]> PR fortran

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-15 Thread patchapp at dberlin dot org
--- Comment #10 from patchapp at dberlin dot org 2007-05-15 13:40 --- Subject: Bug number PR31867 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-05/msg00961.html -- http://gcc.gnu.org/bugzilla/s

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-15 Thread pault at gcc dot gnu dot org
--- Comment #9 from pault at gcc dot gnu dot org 2007-05-15 10:56 --- (In reply to comment #8) > The patch below works and regtests OK. I told a lie - the version that regtests OK has the line + if (!integer_onep (info->stride[dim])) + stride_ne_one = 1; a b

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-14 Thread pault at gcc dot gnu dot org
--- Comment #8 from pault at gcc dot gnu dot org 2007-05-14 20:51 --- The patch below works and regtests OK. I am not convince that this is the whole story and need to think about it for a day or two. Paul Index: gcc/fortran/trans-array.c ==

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-11 Thread pault at gcc dot gnu dot org
--- Comment #7 from pault at gcc dot gnu dot org 2007-05-11 13:13 --- (In reply to comment #6) > So I suspect that the problem lies in the interfacing around > gfc_conv_function_call but I just don't see it yet. Indeed this is the case: In Tobias' #5, changing the declaration for 'wor

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-11 Thread pault at gcc dot gnu dot org
--- Comment #6 from pault at gcc dot gnu dot org 2007-05-11 12:09 --- This gives the correct result: pure integer function lensum (words, sep) character (len=*), intent(in):: words(:), sep lensum = (size (words)-1) * len (sep) + sum (len_trim (words)) end function module ut

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-10 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-05-10 12:34 --- Reduced test case, which gives still the same valgrind error. In addition, len(join(words)) should give 8 not 10. Using "len=5" instead of "len=*" or "words(2)" instead of "words(:) fixes both. (=> "8" and no valgrin

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-09 Thread beliavsky at aol dot com
--- Comment #4 from beliavsky at aol dot com 2007-05-09 15:27 --- (In reply to comment #2) > I get: > words = 'two three' > On x86-64-gnu/linux with latest 4.3 > I wonder if this is one that we recently fixed. Can you try with a more > recent > build? Using Mingw 20070506, the probl

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-08 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-05-09 07:33 --- valgrind shows: ==7067== Syscall param write(buf) points to uninitialised byte(s) ==7067==at 0x5603550: write (in /lib64/libc-2.5.so) ==7067==by 0x4EC1130: do_write (unix.c:336) ==7067==by 0x4EC11D1: fd_

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-05-09 01:33 --- I get: words = 'two three' On x86-64-gnu/linux with latest 4.3 I wonder if this is one that we recently fixed. Can you try with a more recent build? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31867

[Bug fortran/31867] function result with character LEN computed at run time

2007-05-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-05-09 01:10 --- I will look this over tonight. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31867