search for: inferptralignment

Hi all, I've been working on a backend of our architecture and noticed llvm performs following combining although one of operands is FrameIndex. Combining: t114: i64 = add FrameIndex:i64<0>, Constant:i64<56> Creating new node: t121: i64 = or FrameIndex:i64<0>, Constant:i64<56> ... into: t121: i64 = or FrameIndex:i64<0>, Constant:i64<56> This

...sed implementing this one. But, depending on the testcase that I use, implementing it has no or worse effect: I now get assertion errors complaining of different value sizes, coming from the difference between the datalayout (ptrsize:i32) and the pointerty (size overruled to i64). in SelectionDag::InferPtrAlignment. I also found out the this method is not called at all (for my (failing) tests) during the initial selection dag buildup. Note: - most of my testing is done on llvm-3.3, but I verified that the same issues are there for llvm-3.4 - I did implement: virtual MVT getScalarShiftAmountTy(EVT LHSTy)...

The following problems happens with architectures, where stack alignment is smaller than the biggest preferred alignment for any data type SP pointer may point anywhere with alignment of stack alignment (4 in our case) SelectionDAGBuilder however calls CreateStackObject with preferred alignment is given data type(8 in our problemaric case. The ABI alignment for this data type is only 4) This

Hi Hal, On Fri, Apr 4, 2014 at 12:44 AM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "Jeroen Dobbelaere" <jeroen.dobbelaere at gmail.com> > [... ] > > I am trying to get llvm working for an architecture that has 64bit > > registers, but 32bit addresses. > > Because of that, I want the pointers to also be

Hi John, On Tue, 14 May 2019 at 17:51, Joan Lluch <joan.lluch at icloud.com> wrote: > This problem is also shared by the MSP430 target, and it’s very easy to reproduce by just compiling the code that I posted before. That's some good detective work; it definitely explains what you're seeing. Since MSP430 is affected it would probably be pretty easy to upstream an alignment-aware

...vm::TargetLoweringObjectFile::SectionForGlobal(llvm::GlobalValue const*, llvm::Mangler*, llvm::TargetMachine const&) constin libLLVMAsmPrinter.a(AsmPrinter.cpp.o) "llvm::TargetData::getPreferredAlignment(llvm::GlobalVariable const*) const", referenced from: llvm::SelectionDAG::InferPtrAlignment(llvm::SDValue) constin libLLVMSelectionDAG.a(SelectionDAG.cpp.o) llvm::TargetLoweringObjectFileMachO::SelectSectionForGlobal(llvm::GlobalValue const*, llvm::SectionKind, llvm::Mangler*, llvm::TargetMachine const&) constin libLLVMCodeGen.a(TargetLoweringObjectFileImpl.cpp.o) llvm::TargetLoweri...