similar to: [LLVMdev] Target Specific Parsing API

On Wed, December 31, 2014 12:03, Warren Young wrote: > > So, cope with change. > Is one to infer from your mantra 'cope with change' that one is not supposed to express any opinion whatsoever, ever, on any forum; on the externalised cost of changes made to software with no evident technical justification? And that to do so is evidence of some moral or intellectual defect in

I guess this is a more general questoin about reserving io port ranges and interrupts. There was a thread on this some time ago http://lists.xensource.com/archives/html/xen-users/2005-07/msg00659.html and it was supported in xen but not externalised in the tools. Did this ever happen ? The thread also mentions a fake PCI device. How would this be implemented ? Regards, Mike

On Jan 1, 2015, at 2:15 PM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: > On Wed, December 31, 2014 12:03, Warren Young wrote: >> >> So, cope with change. > > Is one to infer from your mantra 'cope with change' that one is not supposed > to express any opinion whatsoever, ever, on any forum No, it?s a reaction to those who apparently want nothing to

Hi Chris, The main benefit for LLVM to include SPIRV support directly is to increase the number of users and developers in the area of heterogeneous computing, e.g. GPUs, FPGAs, DSPs. We want to increase the number of such devices that LLVM natively supports by adding compilation to SPIRV due to the shortage of proprietary backends in upstream LLVM. Just to clarify we are currently suggesting

On Feb 27, 2018, at 10:25 AM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 02/27/2018 05:07 AM, Anastasia Stulova wrote: >>> SPIR-V does not have to be a part of LLVM for you to do this. You can add >>> the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) >>> that uses the external tool to translate