This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 3/7] Add stdint.h wrapper for VxWorks.
On Jun 25, 2012, at 1:15 PM, rbmj wrote:
> On 06/25/2012 04:02 PM, Mike Stump wrote:
>> On Jun 25, 2012, at 12:09 PM, rbmj wrote:
>>> I also do not know how to run the test suite for the target system (powerpc-wrs-vxworks). I would think some sort of powerpc simulator, but I don't have a firmware image for VxWorks - just headers and embedded hardware.
>> To test well, you need to be able to compile and run code. So, the question is, can you do that, or not? If you can, then you have what you need to test. If you cannot do that, then you cannot test well. If you can compile, then you can test the compile time tests, but you'll miss out on all runtime tests.
>>
> Well, I know that I need to be able to compile and run code. I would guess (/hope) that the testsuite is automated though,
It is.
> but I can't use that if I need to use my own custom buildscripts in order to generate executables (can I?).
Yes, you can use it.
> Furthermore, I looked in those files (gcc/testsuite/gcc.dg/c99-stdint* - are these correct?) and I can't find any entry point.
Lots of tests don't require main. A class that does require main are C runtime tests.
> If it helps, I can compile/run code. I know that the original fixincludes patches I had compiled and ran code as well - I built my project and successfully ran it. The problem is I don't exactly know the method. Also, my classes have finished so I no longer have access to a target :-/
Ah, if no access, then, no runtime testing. You can still do compile time testing, if you want.
An easier task might be to ask someone that has a VxWorks testing setup to test for you, there might be someone on the list that has one.