On Dec 22, 2015, at 8:00 AM, Alan Lawrence <alan.lawrence@foss.arm.com> wrote:
On 21/12/15 15:33, Bill Schmidt wrote:
Not on a stage1 compiler - check_p8vector_hw_available itself requires being
able to run executables - I'll check on gcc112. However, both look like they're
really about the host (ability to execute an asm instruction), not the target
(/ability for gcc to output such an instruction)....
Hm, that looks like a pervasive problem for powerpc. There are a number
of things that are supposed to be testing effective target but rely on
check_p8vector_hw_available, which as you note requires executing an
instruction and is really about the host. We need to clean that up; I
should probably open a bug. Kind of amazed this has gotten past us for
a couple of years.
Well, I was about to apologize for making a bogus remark. A really "proper" setup, would be to tell dejagnu to run your execution tests in some kind of emulator/simulator (on your host, perhaps one kind of powerpc) that only/additionally runs instructions for the other, _target_, kind of powerpc...and whatever setup you'd need for all that probably does not live in the GCC repository!
I’m not following. dejagnu can already run tests on the target to makes decisions on which tests to run and what to expect from them, if it wants. Some ports already do this. Further, this is pretty typical and standard and easy to do
You confuse the issue by mentioning host, but this I think is wrong. These decisions have nothing to do with the host. The are properties of the target execution environment.
I’d be happy to help if you’d like. I’d just need the details of what you’d like help with.