On Fri, Apr 3, 2020 at 1:09 PM Liviu Ionescu <i...@livius.net> wrote:

>
>
> 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.
>
>
Reinventing the wheel, GCC already has an extensive testsuite which is
recommended to run to make sure *your* build generates correct binaries:
https://gcc.gnu.org/install/test.html

Although the full suite will take quite a while to run.

/Andreas
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to