search for: irasm

...lapsing an entire directory to a single file, it seems fine and even good when the names align. But this seems somewhat less principled than that. Essentially, consistency is a strong argument. I'm looking for strong arguments for keeping them where they are to counter that. > s/AsmParser/IRASM/ (to be distinguished against MCASM) This is a really good one. I would paint this bikeshed LLParser or IRParser. "Asm" has to go though.

...ent. IMO, I am tolerant of *historical namings*. > Are there other names that are poor choices and are lingering in our > codebases? I'm willing to sign up to do more renames while I'm at > this, so this is a chance to get someone else to do the heavy lifting. > =] s/AsmParser/IRASM/ (to be distinguished against MCASM) s/ExecutionEngine/EE/ (or something like buzzword!) ...Takumi

Hello LLVM & Clang hackers! Based on a discussion with Chris, I would like to propose a Great Renaming of Things for the 3.3-era LLVM and Clang codebase. First and foremost, the two most significant changes I would like to make: 1) llvm/lib/VMCore/... -> llvm/lib/IR/... I've discussed potential names for the VMCore (or LLVMCore) library with lots of folks, and the best idea anyone

...rgument. I'm looking for strong > arguments for keeping them where they are to counter that. Right. IR is central to the compiler backend, but clients of clang or higher level things (who do use a lot of stuff from llvm/* also, directly) don't necessarily use IR). >> s/AsmParser/IRASM/ (to be distinguished against MCASM) > > This is a really good one. > > I would paint this bikeshed LLParser or IRParser. "Asm" has to go though. Personally, I'd like to get llvm/IR and CodeGen->IRGen done, then discuss other movements in separate threads :). But ye...