[Bug fortran/31298] Uninitialized variable in f951 (in read_module) / renaming operator in USE

2007-08-14 Thread burnus at gcc dot gnu dot org
--- Comment #9 from burnus at gcc dot gnu dot org 2007-08-14 21:16 --- (From update of attachment 13369) > strcpy (new->local_name, name); This does not make much sense for INTERFACE_INTRINSIC_OP. The problem with being able to import an operator only once is related to PR 33072: operat

[Bug fortran/31298] Uninitialized variable in f951 (in read_module) / renaming operator in USE

2007-06-23 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2007-06-23 13:41 --- Issue which could be solved by the fix for this PR: PR 29876. -- burnus at gcc dot gnu dot org changed: What|Removed |Added -

[Bug fortran/31298] Uninitialized variable in f951 (in read_module)

2007-05-22 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2007-05-22 13:45 --- (In reply to comment #6) > Tobias, what is the current status on that bug? The attached patch is ok, except it fixes only part of the problem. I got stuck at: operator(+) => operator(.op.) That is: importing an us

[Bug fortran/31298] Uninitialized variable in f951 (in read_module)

2007-05-22 Thread fxcoudert at gcc dot gnu dot org
--- Comment #6 from fxcoudert at gcc dot gnu dot org 2007-05-22 13:31 --- Tobias, what is the current status on that bug? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31298

[Bug fortran/31298] Uninitialized variable in f951 (in read_module)

2007-04-18 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-04-18 10:18 --- (In reply to comment #4) Another thing which needs to be supported: use mod, only: operator(foo) => operator(.op.), & operator(bar) => operator(.op.), & operator(op), &

[Bug fortran/31298] Uninitialized variable in f951 (in read_module)

2007-04-15 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-04-15 20:20 --- Created an attachment (id=13369) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13369&action=view) Updated patch This patch handles almost everything except of operator() => operator(.user.) where could be e.

[Bug fortran/31298] Uninitialized variable in f951 (in read_module)

2007-03-31 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-03-31 22:51 --- Created an attachment (id=13312) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13312&action=view) Preliminary patch > Valgrind gives no error related to uninitialized when compiling with gfortran. I think you

[Bug fortran/31298] Uninitialized variable in f951 (in read_module)

2007-03-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-03-28 04:21 --- Valgrind gives no error related to uninitialized when compiling with gfortran. I am not sure this is a problem of real concern. -- jvdelisle at gcc dot gnu dot org changed: What|Removed

[Bug fortran/31298] Uninitialized variable in f951 (in read_module)

2007-03-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-03-28 02:39 --- I will try this one. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added A