Re: gnat compiler issues with a partial build

[Mark Lorenzen <mark.lorenzen@gmail.com>]

On Thursday, June 4, 2015 at 1:12:27 PM UTC+2, jan.de...@gmail.com wrote:

> jan@janDell:~/MMS/programs-KERNEL/ec-master/obj$ nm memory_copy.o
>                  U __gnat_rcheck_CE_Access_Check
> 0000000000000000 T memcpy
> 0000000000000000 D memory_copy_E
> -------------------------------------
> 
> They are all related to the Exception machinery and refer to about 4 or 5 symbols in "Ada.Exeptions" in the standard "x86 Linux" runtime.
> They are caused by any construct where the compiler suspects that there might be a runtime error under certain conditions. And they have to do with exception propagation I suspect, from looking at a disassembly.
> Now in an zfp runtime, any standard runtime references should be switched off in the compiler, or else an alternative should be supplied in the custom runtime. But both ravenscar and zfp (ex Adacore) do not cater for this eventuality.
> 
> Needless to say that I have been through all exception related pragmas and restrictions. And I did make a 'gnat.adc' file that is duly noted in the project file. So that any pragmas are global.

I don't know what you are trying to achieve, but it seems to me, that you want to build your module with a ZFP run-time that you don't have...

Can you build your module with run-time checks disabled? This should ensure that the access check code is not emitted and therefore does not refer to the undefined symbol __gnat_rcheck_CE_Access_Check.

Regards,

MarkL