View previous topic :: View next topic |
Author |
Message |
DanRRight
Joined: 10 Mar 2008 Posts: 2815 Location: South Pole, Antarctica
|
Posted: Sun Mar 10, 2013 5:59 pm Post subject: Option for SLINK to be more verbose |
|
|
When SLINK informs if it finds common blocks size different in different subprograms or symbols/variables/functions are missing, it only says about the file names where problems were found. But under these filenames there could be literally hundreds of subprograms. If there is no option to force it to be more specific (and i do not see it but may be overlooked) my suggestion is to create one. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
Posted: Sun Mar 10, 2013 10:42 pm Post subject: |
|
|
Thanks for the input. I think that this suggestion has been made before.
However, I doubt that SLINK has access to this information until it
is first passed through as data in the object file by FTN95. So it becomes a major undertaking for a small gain. |
|
Back to top |
|
|
JohnCampbell
Joined: 16 Feb 2006 Posts: 2554 Location: Sydney
|
Posted: Wed Mar 13, 2013 12:58 am Post subject: |
|
|
Paul,
Wouldn't SLINK have access to the subroutine/function name where the inconsistent COMMON length is being defined ? When processing a .obj or .lib file, doesn't it processes one routine at a time.
John |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
Posted: Wed Mar 13, 2013 9:33 am Post subject: |
|
|
You may be right. It is on the wish list. |
|
Back to top |
|
|
|