On 06/17/15 04:57, James Greenhalgh wrote:
I'm seeing the same issues on aarch64-none-elf and aarch64_be-none-elf in one of my testing environments, but, interestingly, not on aarch64-none-linux-gnu or in my other aarch64-none-elf testing environment (!!).
ugh. What is the behavior on the testcase with the patch reverted? Is it the same on both elf systems? (I'm expecting an ICE in one of the tsubst variants when it meets a DEFAULT_ARG)
I've pasted both log extracts below (after stripping the file paths for each build environment, so you can see just how similar the invocations are!). The PASSing environment does use a slightly more modern toolchain for building the cross-toolchain (PASSing environment uses 4.9.2, FAILing environment uses 4.8.1), so that could be a source of the difference?
ew. nathan
