[Bug fortran/25818] Problem with handling optional and entry master arguments

2006-07-31 Thread taschna at uni-muenster dot de
--- Comment #5 from taschna at uni-muenster dot de 2006-07-31 07:49 --- (In reply to comment #3) Steve, > [...]It's more a question of "why is it a NULL pointer?" not > whether we can work around the NULL pointer. i finally found Paul's mail corresponding to

[Bug fortran/25818] Problem with handling optional and entry master arguments

2006-07-30 Thread taschna at uni-muenster dot de
--- Comment #4 from taschna at uni-muenster dot de 2006-07-31 06:32 --- (In reply to comment #3) Steve, > Thanks for the patch, but I think it is only covering up the real > problem. It's more a question of "why is it a NULL pointer?" not > whether we can work

[Bug fortran/25818] Problem with handling optional and entry master arguments

2006-07-27 Thread taschna at uni-muenster dot de
--- Comment #2 from taschna at uni-muenster dot de 2006-07-27 22:38 --- I'm an absolute beginner in programming gfortran, but the following patch seems to solve this bug by inserting an if-block into the code in order to prevent the access to the NULL pointer in case the arr

[Bug debug/25324] New: Wrong DW_TAG_compile_unit generated when compiling preprocessed fortran code

2005-12-08 Thread taschna at uni-muenster dot de
and therefore "should not be mentioned in debugging information". -- Summary: Wrong DW_TAG_compile_unit generated when compiling preprocessed fortran code Product: gcc Version: 4.0.2 Status: UNCONFIRMED Severity: normal