#31 closed defect (fixed)
GFortran bug?
| Reported by: | Dave Offiler | Owned by: | marq |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0 |
| Component: | ropp_utils | Version: | 0.8 |
| Keywords: | Cc: | dave.offiler@…, carlo.buontempo@…, axel.vonengeln@… |
Description
GFortran (gfc 4.1.0) gives internal error segmentation fault when compiling ropp_tools/arrays/copy_alloc.f90 on line 71 of copy_alloc_1D_Text
if (associated(newarray)) deallocate(newarray)
Futher investigation shows that the same line in every copy_alloc_nD_Text routine (NB ONLY Text versions, NOT any other data type). The error does not appear if the routine is cut out on it's own without the USE arrays generic interface.
Most likely a bug in GFortran, but this needs pinning down before reporting the bug to gfc developers (The offending line to my mind is a bit dodgy anyway, and at best makes some assumtions about the pre-existing status of newarray)
Change history (4)
comment:1 by , 19 years ago
| Cc: | added |
|---|---|
| Milestone: | → 0.9 |
| Version: | 0.8 |
comment:2 by , 19 years ago
| Milestone: | 0.9 → 1.0 |
|---|
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 by , 18 years ago
| Version: | → 0.8 |
|---|
Note:
See TracTickets
for help on using tickets.
GFortran (gfc v4.2.0) compiles all code in ropp_tools with no errors. If this was indeed a compiler bug, it appears to have ben fixed.
The code is still dubious to my mind.