search for: d27503

> On Apr 4, 2017, at 11:44 AM, John McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> On Apr 4, 2017, at 2:12 PM, Matthias Braun <matze at braunis.de <mailto:matze at braunis.de>> wrote: >> My two cents: >> >> - I think inline assembly should work even if the compiler cannot parse the contents. This would rule out msvc inline assembly

Hi, I'm trying to implement a target-agnostic intrinsic, first targeting X86. I'm trying to map the intrinsic SD node to an instruction with a certain target opcode that I've introduced. The issue that I'm running into is what the correct way to lower the argument is. I've done a couple loops on the docs so any help would be appreciated! Some options I've explored but have

That’s a very good point, the X-ray data that would be useful for the linker should be collected from a "profile-use” build to be accurate. IIUC, that’d look like: build with profile-gen -> run benchmarks -> build with profile-use + Xray -> run benchmarks -> build with profil-use and feed linker with X-ray data for layout optimization. — Mehdi > On Jan 16, 2017, at 8:25