Displaying 5 results from an estimated 5 matches for "hasreservedcallfram".
Did you mean:
hasreservedcallframe
2012 Nov 27
1
[LLVMdev] strange dbgs() behavior: unable to print floats in machine backend
...s ago, and thus got the "explicit". PrintReg constructor. When I do not include raw_ostream.h after including Debug.h in the backend cpp files, I now get compilation errors, not only when trying to print floats but also in other places. For example, for the code
bool ADRESRegisterInfo::hasReservedCallFrame(const MachineFunction &MF) const {
dbgs() << "hasReservedCallFrame() = " << !MF.getFrameInfo()->hasVarSizedObjects() << "\n";
return !MF.getFrameInfo()->hasVarSizedObjects();
}
I get
llvm[0]: Compiling ADRESRegisterInfo.cpp for Debug+Asserts b...
2012 Nov 27
0
[LLVMdev] strange dbgs() behavior: unable to print floats in machine backend
Can you try making the constructor "explicit" for PrintReg in
include/llvm/Target/TargetRegisterInfo.h. I think you were getting an
implicit conversion there which should probably be fixed anyway.
On Mon, Nov 26, 2012 at 11:47 PM, Bjorn De Sutter <
bjorn.desutter at elis.ugent.be> wrote:
> Hi,
>
> that solved my problem on trunk as well, thanks. Strange that you have to
2012 Nov 27
2
[LLVMdev] strange dbgs() behavior: unable to print floats in machine backend
Hi,
that solved my problem on trunk as well, thanks. Strange that you have to include this though.
Bjorn
On 27 Nov 2012, at 00:00, Daniel Prokesch <daniel.prokesch at gmail.com> wrote:
> Hi,
>
> I accidentally stumbled upon your post.
> I observed similar behaviour whenever I did not include
>
> #include "llvm/Support/Debug.h"
> #include
2011 Sep 09
1
[LLVMdev] Reserved call frame
Hello,
i am trying to disable reserved call frame from the x86 backend, by
setting hasReservedCallFrame function, in
lib/Target/X86/X86RegisterInfo.cpp to always return false. When doing
this i get the correct frame size,
and the sub/add rsp instructions around the call correctly, but it seems
that the offsets from rsp are not
correctly updated between the sub instruction and the call.
Is this so...
2017 Apr 27
4
-msave-args backend support for x86_64
...Lowering.cpp (working copy)
@@ -47,6 +47,7 @@
// standard x86_64 and NaCl use 64-bit frame/stack pointers, x32 - 32-bit.
Uses64BitFramePtr = STI.isTarget64BitLP64() || STI.isTargetNaCl64();
StackPtr = TRI->getStackRegister();
+ SaveArgs = STI.getSaveArgs();
}
bool X86FrameLowering::hasReservedCallFrame(const MachineFunction &MF) const {
@@ -83,7 +84,7 @@
/// or if frame pointer elimination is disabled.
bool X86FrameLowering::hasFP(const MachineFunction &MF) const {
const MachineFrameInfo &MFI = MF.getFrameInfo();
- return (MF.getTarget().Options.DisableFramePointerElim(MF) ||
+...