(j3.2006) TKR for C Interop

Bill Long longb
Wed Feb 28 11:06:53 EST 2007

Aleksandar Donev wrote:

>Bill Long wrote:
>>The reason was to give vendors enough information to 
>>create valid dope vectors.
>This information can be filled by the Fortran callee. The callee knows 
>what the TKR signature is, and all it needs from the caller are the 
>bounds and strides and base address. 

You made that same argument before and it was rejected.  It is a 
frustrating waste of everyone's time to continually restart arguments 
you have lost before.

>In fact, at least one vendor has 
>exactly those and only those fields in the descriptor. And if the callee 
>is in C, it does not need a "valid" dope vector, it just needs a vector 
>it can extract bounds and base address from.
>>Not just one vendor, but all the vendors.  
>No, look at NAGs descriptors, they are publicly documented. 

As I explicitly said, "Not just one vendor".  I know you want everyone 
to change their dope vectors to be just like NAGs so you will have 
complete documentation,  It is not going to happen.  Period.  Unless you 
have some NEW idea that has not already been discussed and rejected, it 
is pointless to continue this thread.


>TKR info 
>does NOT need to be included in a descriptor to implement fortran, any 
>variant of it up to know. For polymorphic arguments, a type descriptor 
>is needed, which could be separate from the array descriptor (but does 
>not have to be).
>>This is a basic implementation and performance issue.  To say that the 
>>TKR information is "useless" without these other features is just nonsense.
>You just want to make the Fortran routine more efficient (by a miniscule 
>amount), namely, so it does not have to do any massaging of the passed 
>descriptor, while making the life of the programmer that needs to 
>construct said descriptors and the API sooo much more complicated. 
>Either make the API minimal (but less functional), or complex (but 
>functional). Anything in-between is nonsense.
>J3 mailing list
>J3 at j3.scs.gmu.edu

Bill Long                                   longb at cray.com
Fortran Technical Support    &              voice: 651-605-9024
Bioinformatics Software Development         fax:   651-605-9142
Cray Inc., 1340 Mendota Heights Rd., Mendota Heights, MN, 55120


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://j3.scs.gmu.edu/pipermail/j3/attachments/20070228/e10c71cd/attachment.html 

More information about the J3 mailing list