search for: dumpres

Displaying 11 results from an estimated 11 matches for "dumpres".

Did you mean: dumpers
2010 Jan 15
3
[LLVMdev] [PATCH] SelectionDAG Debugging
On Jan 15, 2010, at 1:38 PM, David Greene wrote: > On Friday 15 January 2010 15:09, Dan Gohman wrote: > >>> Sound good? reimplement >> >> Unlimited-recursion dumping is what the existing dump routines >> already do, so it's a little odd to have a flag to allow these > > Which existing dump routines are you referring to? dumpr(). I guess it wasn't
2010 Jan 15
0
[LLVMdev] [PATCH] SelectionDAG Debugging
On Friday 15 January 2010 16:23, Dan Gohman wrote: > On Jan 15, 2010, at 1:38 PM, David Greene wrote: > > On Friday 15 January 2010 15:09, Dan Gohman wrote: > >>> Sound good? reimplement > >> > >> Unlimited-recursion dumping is what the existing dump routines > >> already do, so it's a little odd to have a flag to allow these > > > >
2010 Jan 16
1
[LLVMdev] [PATCH] SelectionDAG Debugging
On Jan 15, 2010, at 2:34 PM, David Greene wrote: > On Friday 15 January 2010 16:23, Dan Gohman wrote: >> On Jan 15, 2010, at 1:38 PM, David Greene wrote: >>> On Friday 15 January 2010 15:09, Dan Gohman wrote: >>>>> Sound good? reimplement >>>> >>>> Unlimited-recursion dumping is what the existing dump routines >>>> already do,
2011 Jan 08
2
Wine-1.3.11 will not compile for me
.../sheridan/Let?lt?s/wine-1.3.11/tools/wrc' gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -DINCLUDEDIR="\"/usr/local/include/wine\"" -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wpointer-arith -g -O2 -o dumpres.o dumpres.c gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -DINCLUDEDIR="\"/usr/local/include/wine\"" -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wpointer-arith -g -O2 -o genres.o genres.c gcc -c -I. -I....
2013 Jul 31
0
[LLVMdev] Help with promotion/custom handling of MUL i32 and MUL i64
Hi Dan, If you set the node's action to "Custom", you should be able to interfere in the type legalisation phase (before it gets promoted to a 64-bit MUL) by overriding the "ReplaceNodeResults" function. You could either expand it to a different libcall directly there, or replace it with a target-specific node (say XXXISD::MUL32) which claims to take i64 types but you
2013 Jul 31
1
[LLVMdev] Help with promotion/custom handling of MUL i32 and MUL i64
Thanks Tom. I really appreciate your insight. I'm able to use the customize to get the 64-bit to go to a subroutine and for the 32-bit, I am generate XXXISD::MUL32. I'm not sure then what you mean about "overriding" the ReplaceNodeResults. For ReplaceNodeResults, I'm doing: SDValue Res = LowerOperation(SDValue(N, 0), DAG); for (unsigned I = 0, E =
2009 Dec 18
2
[LLVMdev] [PATCH] dbgs() Use
Here's an example patch of how dbgs() will be used. Essentially I will replace uses of errs() with dbgs(). I believe this is the correct thing to do because: - With #define NDEBUG, dbgs() == errs() - With debugging and -debug-buffer-size=0 (the default), dbgs() just passes output to errs(). - When -debug-buffer-size>0, you want to buffer ALL output so that you don't get some
2013 Jul 31
2
[LLVMdev] Help with promotion/custom handling of MUL i32 and MUL i64
Thanks for the information, allow maybe I can re-phrase the question or issue. Assume 64-bit register types, but integer is 32-bit. Already have table generation of the 64-bit operation descriptions. How about this modified approach? Before type-legalization, I'd really like to move all MUL I64 to a subroutine call of my own choice. This would be a form of customization, but I want this
2010 Jan 15
2
[LLVMdev] [PATCH] SelectionDAG Debugging
On Jan 15, 2010, at 11:51 AM, David Greene wrote: > On Friday 15 January 2010 13:41, Dan Gohman wrote: >> On Jan 15, 2010, at 11:31 AM, David Greene wrote: >>> On Friday 15 January 2010 13:16, Dan Gohman wrote: >>>> Is it ever desirable to pass false to the "limit" argument? >>> >>> Not in the usual course of things but I figured someday
2010 Jan 15
0
[LLVMdev] [PATCH] SelectionDAG Debugging
On Friday 15 January 2010 15:09, Dan Gohman wrote: > > Sound good? reimplement > > Unlimited-recursion dumping is what the existing dump routines > already do, so it's a little odd to have a flag to allow these Which existing dump routines are you referring to? > new dump routines to do the same thing. I guess you could > refactor the old ones to call the new ones and
2010 Dec 01
3
Error While installing Wine on OSX version 10.4.1.1!!
...> :info:build config.status: creating tools/wmc/Makefile > :info:build config.status: creating tools/wrc/Makefile > :info:build ../../tools/makedep -C. -S../.. -T../.. lang.c mcl.c utils.c wmc.c write.c mcy.y > :info:build ../../tools/makedep -C. -S../.. -T../.. dumpres.c genres.c newstruc.c readres.c translation.c utils.c wrc.c writeres.c parser.y parser.l > :info:build make[1]: Nothing to be done for `all'. > :info:build make[1]: Nothing to be done for `all'. > :info:build make[1]: Nothing to be done for `all'. > :info:build...