Re: pragma import => pointer in mapping table ?

[Per Sandberg <per.sandberg@sandat.dyndns.org>]

You have asked some question about some very low level details in some
implementation, but may i ask what is it you want to achive by reading
.map-files, wont the linker just solve your problem ??
If you got some header files that are reasonably clean what don't just:
	"g++ -fdump-ada-spec"
 and be happy ??
/Per


 On Tue, 5 Nov 2013 01:49:31 -0800 (PST)
wkernow@gmail.com wrote:

> Hello,
> 
> This is the first time I write in a newsgroup.
> 
> In my code, I have : 
> 
> pragma import (C, X, "varX_C");
> 
> with everything that I need before (pragma convention, declaration of
> varX, "X_C" comes from a C file) 
> 
> Code is ok but my problem is about mapping file. Mapping table is a
> file which identifies each variable by an address. This file come
> from toolchain (varX 0x01891234)
> 
> In deed, I saw that all variables X derived from a "pragma import"
> are considered as pointers in mapping table whereas variables type of
> varX are not access types (basic types).
> 
> My hypothesis is that pragma import create an access to C data
> "varX_C" from a exterior point of view of ada code (so by mapping
> table).
> 
> To confirm my hypothesis, 2 questions : 
> 1) Are you ok ?
> 2) Is possible to define an option in toolchain in order to define
> adressing mode (for addresses in mapping file from pragma import) in
> direct mode (on ADA data) instead of indirect mode (on C data). Or is
> it a default option ?
> 
> if I'm wrong or you don't understand :
> 3) In genaral, I don't understand how a basic variable (type BOOLEAN)
> in ADA code can be considered as a pointer to a BOOLEAN in an mapping
> file derived from toolchain ?
> 
> Thank you