[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2014-10-04 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36534 --- Comment #12 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org --- Author: fxcoudert Date: Sat Oct 4 10:18:07 2014 New Revision: 215887 URL: https://gcc.gnu.org/viewcvs?rev=215887root=gccview=rev Log: PR fortran/36534 *

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2014-10-04 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36534 Francois-Xavier Coudert fxcoudert at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2014-09-29 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36534 Bug 36534 depends on bug 37173, which changed state. Bug 37173 Summary: Check whether intrinsic assignment between character kind=1 / 4 is allowed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37173 What|Removed

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2014-09-27 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36534 Francois-Xavier Coudert fxcoudert at gcc dot gnu.org changed: What|Removed |Added Status|NEW

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2010-05-02 Thread dfranke at gcc dot gnu dot org
--- Comment #11 from dfranke at gcc dot gnu dot org 2010-05-02 14:31 --- Assuming PR37173 is correct, isn't this example invalid anyway (as already noted by Tobias in #4)? Instead, it should probably be written as: CHARACTER (kind=4,len=*) MY_STRING4(1:3) PARAMETER ( MY_STRING4 =

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2010-04-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2010-04-13 04:31 --- With current trunk (4.6) I see this: $ valgrind --leak-check=full f951 parameter_array_init_4.f90 --- snip --- ==12209== 48 bytes in 6 blocks are definitely lost in loss record 21 of 352 ==12209==at

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2009-12-05 Thread tkoenig at gcc dot gnu dot org
--- Comment #6 from tkoenig at gcc dot gnu dot org 2009-12-05 18:28 --- $ cat huhu.f90 CHARACTER (kind=4,len=*) MY_STRING4(1:3), my_string_s4 PARAMETER ( MY_STRING4 = (/ A , B, C /) ) end $ gfortran huhu.f90 huhu.f90:1.54: CHARACTER (kind=4,len=*) MY_STRING4(1:3), my_string_s4

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2009-12-05 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2009-12-05 18:54 --- (In reply to comment #5) It looks like this is fixed. I could not reproduce the problem. I still get this problem: $ cat fhjfff.f90 CHARACTER (kind=4,len=*) MY_STRING4(1:3) PARAMETER ( MY_STRING4 = (/ A , B, C /)

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2009-12-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-12-06 00:16 --- I can not reproduce at all. Can you try an update. Maybe one our patches recently fixed this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36534

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2009-12-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-12-06 01:02 --- OK we have a Heisenbug going on here. Running from Valgrind like this: valgrind --leak-check=full f951 -pedantic untitled.f ==14463== Memcheck, a memory error detector. ==14463== Copyright (C) 2002-2007, and

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2009-12-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-12-05 06:56 --- It looks like this is fixed. I could not reproduce the problem. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36534

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2008-08-24 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2008-08-24 10:38 --- One could work around the bug: As such conversions are not valid, one just needs to reject them with -pedantic (cf. PR 37173) ;-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36534

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2008-08-23 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|fxcoudert at gcc dot gnu dot|unassigned at gcc dot gnu |org

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2008-07-18 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2008-07-18 13:28 --- Note: The test case parameter_array_init_4.f90 (Rev. 137950) now avoids the conversion by using kind-4 literals. However, the bug itself is still present. See example in comment #0. --

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2008-07-09 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2008-06-13 Thread fxcoudert at gcc dot gnu dot org
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2008-06-13 23:06 --- I love that one: Fixed-form is likely to be F77/legacy. Well, the issue is that I don't think we have a way to tell, from the sym, that it's a internal conversion function. Maybe the crude way, check if the name

[Bug fortran/36534] Bogus: '__convert_s1_s4' at (1) is obsolescent in fortran 95

2008-06-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2008-06-14 05:14 --- *** Bug 36535 has been marked as a duplicate of this bug. *** -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added