setPacketIn($UN.cast{natLt(127)}(4), u8(0)) // To test compile
I get errors:
S2-Postiats-0.2.4/ccomp/runtime -O0 -Wall -mcpu=arm926ej-s
-mthumb-interwork -ffunction-sections -fdata-sections -c -o a.o a_dats.c
In file included from a_dats.c:33:0:
…
^
In file included from DATS/process_dats.c:15:0:
DATS/process_dats.c: In function
’ATSLIB_056_prelude__array_set_at_gint__80__1’:
DATS/process_dats.c:9248:31: error: ‘PMVtmpltcstmat’ undeclared (first use
in this function)
ATSINSmove_void(tmpret303__1,
PMVtmpltcstmat[0](ptr0_set<S2Eapp(S2Ecst(g0uint_t0ype);
S2Eextkind(atstype_uint8))>)(tmp304__1, arg2)) ;
^
…
^
DATS/process_dats.c:9248:49: error: ‘ptr0_set’ undeclared (first use in
this function)
ATSINSmove_void(tmpret303__1,
PMVtmpltcstmat[0](ptr0_set<S2Eapp(S2Ecst(g0uint_t0ype);
S2Eextkind(atstype_uint8))>)(tmp304__1, arg2)) ;
^
If I just try to access packetIn[] directly, I get the same errors. The
code in a.dats is well established working code, and this is the first time
I have tried to access it from a second dats file.
setPacketIn($UN.cast{natLt(127)}(4), u8(0)) // To test compile
I get errors:
S2-Postiats-0.2.4/ccomp/runtime -O0 -Wall -mcpu=arm926ej-s
-mthumb-interwork -ffunction-sections -fdata-sections -c -o a.o a_dats.c
In file included from a_dats.c:33:0:
…
^
In file included from DATS/process_dats.c:15:0:
DATS/process_dats.c: In function
‘ATSLIB_056_prelude__array_set_at_gint__80__1’:
DATS/process_dats.c:9248:31: error: ‘PMVtmpltcstmat’ undeclared (first use
in this function)
ATSINSmove_void(tmpret303__1,
PMVtmpltcstmat[0](ptr0_set<S2Eapp(S2Ecst(g0uint_t0ype);
S2Eextkind(atstype_uint8))>)(tmp304__1, arg2)) ;
^
…
^
DATS/process_dats.c:9248:49: error: ‘ptr0_set’ undeclared (first use in
this function)
ATSINSmove_void(tmpret303__1,
PMVtmpltcstmat[0](ptr0_set<S2Eapp(S2Ecst(g0uint_t0ype);
S2Eextkind(atstype_uint8))>)(tmp304__1, arg2)) ;
^
If I just try to access packetIn directly, I get the same errors. The
code in a.dats is well established working code, and this is the first time
I have tried to access it from a second dats file.
This message means that ptr0_set<…> is unavailable. This is
due to no implementation of ptr0_set being available to the compilerOn Sat, Nov 21, 2015 at 9:59 PM, Mike Jones proc...@gmail.com wrote:
Can you explain how to get that from the message so I can self serve next
time?