[LLVMdev] More ARM asan failures - Line number
eugenis at google.com
Wed Oct 8 05:45:48 PDT 2014
Android is arm-linux-androideabi. Historically there were a few cases
in llvm/clang where a switch handled a number of *eabi variants but
On Wed, Oct 8, 2014 at 4:41 PM, Renato Golin <renato.golin at linaro.org> wrote:
> On 8 October 2014 13:17, Evgeniy Stepanov <eugenis at google.com> wrote:
>> Did it ever work?
> I really don't know. I'm just trying to make it work now and haven't
> tried it before for real.
>> The test says XFAIL: arm-linux-gnueabi.
>> We know that it works on Android-arm, which is essentially the same,
>> maybe with a few different default settings in the driver.
> This platform is hard-float, that's why the XFAIL doesn't work. But
> I'm surprised that it passes on Android (which is arm-gnueabi) and not
> on "arm-linux-gnueabi".
> Anyway, do you think we should mark all the failing tests XFAIL on
> gnueabihf for now?
I don't mind.
> We can at least have a green buildbot and work on them later. I'm not
> particularly worried about ASAN for now, just making sure I can
> compile compiler-rt and use it for the next step, running the
> test-suite with it. But I can't do that while this bot is red.
More information about the llvm-dev