I’m writing an application for a Cypress FX3 USB device which has a 32bit
ARM A9 core. My goal is to extend an existing Makefile to compile some ATS
and call it from C in the ThreadX Application Thread.
I was looking at the make files for arduino_ats, which is where I
prototyped, and now I need to understand some things:
What is ATSTYPE_VAR_SIZE_ and how do you format the value? (I assume
perhaps it should be 0xFFFFFFFF for a 32 bit machine?)
What do each of these do? (-Wno-unused-variable -Wno-unused-label
-Wno-unused-but-set-variable)
What is ATSTYPE_VAR_SIZE_ and how do you format the value? (I assume
perhaps it should be 0xFFFFFFFF for a 32 bit machine?)
ATSTYPE_VAR_SIZE_ is a placeholder.
It is meant to “cheat” the C compiler; it should not really be needed.
In the future, the C code generated by ATS compiler may be analyzed to
remove
the need for ATSTYPE_VAR_SIZE_
What do each of these do? (-Wno-unused-variable -Wno-unused-label
-Wno-unused-but-set-variable)
The C code generated from ATS source contains unused variables, unused
labels, etc. The flags are used
to suppress potential warnings from gcc or clang.On Tuesday, November 17, 2015 at 1:25:05 PM UTC-5, Mike Jones wrote:
I’m writing an application for a Cypress FX3 USB device which has a 32bit
ARM A9 core. My goal is to extend an existing Makefile to compile some ATS
and call it from C in the ThreadX Application Thread.
I was looking at the make files for arduino_ats, which is where I
prototyped, and now I need to understand some things:
What is ATSTYPE_VAR_SIZE_ and how do you format the value? (I
assume perhaps it should be 0xFFFFFFFF for a 32 bit machine?)
What do each of these do? (-Wno-unused-variable -Wno-unused-label
-Wno-unused-but-set-variable)