Displaying 7 results from an estimated 7 matches for "printreg".
Did you mean:
printres
2012 Nov 27
1
[LLVMdev] strange dbgs() behavior: unable to print floats in machine backend
Hi Craig,
I updated from the trunk some minutes 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) co...
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, t...
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
2019 Apr 11
2
Upper case vs lower case in printed and parsed MIR
...t we cannot import exported MIR without manually 'lower casing' it first which is obviously rather annoying.
Looking in https://llvm.org/docs/MIRLangRef.html it is stated that instruction names are case sensitive.
For register names it appear that they are lower cased before printing (see printReg in TargetRegisterInfo.cpp) and to match the definitions are also lower cased before loaded into the parser (see PerTargetMIParsingState::initNames2Regs in MIParser.cpp). For sub-register index names the latter happens but they are currently printed with their original casing witch leads to our prob...
2005 Mar 15
1
Excessive chaining or multiple comboot files
...ader so I was thinking / hoping that I
could "modify" the SysLinux loader to do these things.... since I assuming
it has a multiple stage loader that allows a "Stage 2" loader to do more
things.
What I was hoping was the following psuedo code:
run memtwk.c32
run maxfans.c32
run printregs.c32
run orginal_bootsector.bs
I've tried looking in the source code... and looking for some examples of
SYSLINUX.CFG files... but can't seem to gain traction on the issue.
So; I turn to the "experts" to see if this is:
1) already available? (doubt it but thought I'd ask)
2...
2014 Mar 12
3
[LLVMdev] llc debug info
I can generate debug info using opt like this:
opt < a.bc > /dev/null -mypass -debug
But I don't know how to do it using llc.
I check http://llvm.org/docs/CommandGuide/llc.html
there are not any information about debug flags.
Purpose
EX:
I want to print all the DEBUG(dbgs()......) in
llvm/lib/CodeGen/RegAllocGreedy.cpp .
What should I do?
-------------- next part --------------
An HTML
2013 Oct 09
4
[LLVMdev] Subregister liveness tracking
On Oct 8, 2013, at 2:06 PM, Akira Hatanaka <ahatanak at gmail.com> wrote:
> What I didn't mention in r192119 is that mthi/lo clobbers the other sub-register only if the contents of hi and lo are produced by mult or other arithmetic instructions (div, madd, etc.) It doesn't have this side-effect if it is produced by another mthi/lo. So I don't think making mthi/lo clobber the