> On 3 Apr 2020, at 13:49, Paul Fertser <fercer...@gmail.com> wrote:
>
> Not sure what kind of tests do you have in mind?
I'm not sure either how far should I go with these tests.
For example, I test the arm-none-eabi-gcc xPack by compiling two simple hello
world, one with c and one with c++, with and without -flto; the purpose is to
make the compiler use as many execution paths as possible, so if there are any
missing plug-ins or libraries, to identify this. I'm definitelly not doing
functional tests, to see if the compiler generates the correct code, I expect
these test to be done by those who maintain the compiler.
Similarly for the QEMU Arm xPack, I prepared some semihosted applications and
I'll use them to check if the emulation succeeds.
For OpenOCD, the only test I do now during the build, is to check if it starts.
This proves that all shared libraries are present, and there are not obvious
mistakes, like early segmentation faults.
I do not have any failures in mind, so anything in addition to this, is a
bonus. The only requirement is to run on all my target platforms.
Regards,
Liviu
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
