| View previous topic :: View next topic |
| Author |
Message |
Alexey A. Romanenko
Joined: 17 Feb 2012
Posts: 31
|
 Posted: Wed Mar 27, 2013 3:19 am Post subject: PGF90 inline problem |
 |
|
Hi Mat,
I tried to inline some function with -Minline=XXXX key.
Compiler reported
| Code: | | PGF90-S-0274-Unable to access file XXXX/TOC |
and, I suppose, didn't inline XXXX subroutine.
What does this message means?
Alexey |
|
| Back to top |
|
 |
mkcolg
Joined: 30 Jun 2004
Posts: 4996
Location: The Portland Group Inc.
|
| Posted: Wed Mar 27, 2013 10:02 am Post subject: |
|
|
Hi Alexey,
| Quote: | | PGF90-S-0274-Unable to access file XXXX/TOC |
This is the error you get when trying to use an non-existent inline library. Though, you should only see it if you're using the "lib" sub-option. What's the exact -Minline flag being used?
For example: | Code: |
% pgf90 -o a a.f90 -Minfo=inline -Minline=lib:foo
PGF90-S-0274-Unable to access file foo/TOC |
- Mat |
|
| Back to top |
|
|
Alexey A. Romanenko
Joined: 17 Feb 2012
Posts: 31
|
| Posted: Wed Mar 27, 2013 9:28 pm Post subject: |
|
|
Hi Mat,
XXXX subroutine is not in extern library or what. It is located in the same module as routine, say YYYY, which has 'call XXXX()'.
I sent my example to trs@pgroupp[dot]com
Alexey |
|
| Back to top |
|
|
mkcolg
Joined: 30 Jun 2004
Posts: 4996
Location: The Portland Group Inc.
|
| Posted: Thu Mar 28, 2013 8:17 am Post subject: |
|
|
Hi Alexey,
Wow, that's an odd one. It seems to be a new bug in 13.3 where a number in the function name is causing the driver to parse it as a library name. I've reported it as TPR#19240. The work around would be to add the "name" sub-option before the function name. For example: -Minline=name:foo3
Thanks,
Mat |
|
| Back to top |
|
|
Alexey A. Romanenko
Joined: 17 Feb 2012
Posts: 31
|
| Posted: Thu Mar 28, 2013 6:25 pm Post subject: |
|
|
| Thanks Mat! |
|
| Back to top |
|
|
|
Search
Memberlist
Register
Profile
Log in
