search for: d12660

...se 'opt' wasn't initializing asm parsers, something I am fixing). However, I had a test case failure in test/LTO/X86/current-section.ll, which has module asm, but no target triple. However, it does have a "REQUIRES: default_triple". Mehdi, looks like you added this as part of D12660. I found that this is set to true in test/lit.cfg, and when I print out the config.target_triple there it is x86_64-unknown-linux-gnu. But when I print out the target triple on the Module in CollectAsmUndefinedRefs it is null. How is the config.target_triple supposed to propagate into the test - I...

...ing tests and abstract the “features” > they are using, but this does not seem like a small enough task that I can > commit to an ETA now or have an estimate about when it’ll come on top of > my stack. > > This is why I tried to offer an alternative with > http://reviews.llvm.org/D12660 ; to identify the tests that rely on the > default triple using a generic default_triple feature. > > > > Paul - If we introduce the type of flag your talking about, we should > probably have a discussion about which classes of backends LLVM supports > and try to create a *do...

On 09/04/2015 10:25 AM, Robinson, Paul via llvm-dev wrote: > >> -----Original Message----- >> From: James Y Knight [mailto:jyknight at google.com] >> Sent: Friday, September 04, 2015 10:12 AM >> To: Mehdi Amini; Mehdi Amini via llvm-dev >> Cc: Robinson, Paul >> Subject: Re: [llvm-dev] Testing "normal" cross-compilers versus GPU >> backends

> On Sep 4, 2015, at 10:19 AM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > >>>>> Krzysztof suggested much the same thing that I think you are currently >>>>> doing, which is deliberately configure a default triple but exclude >> the >>>>> corresponding backend. >>>> >>>> You and Takumi were