Hi, I've been reading the docs, including "Creating an LLVM project", and I was wondering if this setup also applies to backends. On one hand it would be good if it did because it would allow one to develop a backend without tracking the LLVM sources with it. If it is not possible (and one follows the instruction of the backend documentation "Writing an LLVM Compiler Backend"), then all our files will be within LLVM sources and they will end up being tracked in the backend repository probably inducing painful merges each time we want to update the LLVM version we are tracking. Would it work using the sample project, creating a lib/Target/mytarget and go from there? Cheers, -- PMatos
Anton Korobeynikov
2010-Apr-29 13:20 UTC
[LLVMdev] Is a backend considered an LLVM project?
Hello> Would it work using the sample project, creating a lib/Target/mytarget > and go from there?Unfortunately, backend != "Project using LLVM" and thus should be tracked with LLVM sources. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
Anton Korobeynikov <anton at korobeynikov.info> writes:> Hello > >> Would it work using the sample project, creating a lib/Target/mytarget >> and go from there? > Unfortunately, backend != "Project using LLVM" and thus should be > tracked with LLVM sources.Ah, that's exactly what I wanted to know. Thanks for the prompt answer. -- PMatos