search for: xxxiseldagtodag

...coding takes place in target lowering and DAG to DAG. The average person doing porting should not, IMO, be exposed to many of the details of chains, glue and other complexities and idiosyncrasies of the Selection DAG. The main idea is to eliminate or shrink considerably XXXTargetLowering and XXXISelDagToDag. There could also be some Machine IR added to the current IR that is not target specific. My 2c. Reed

Hi, Today I downloaded LLVM 1.8 (until yesterday I used 1.7) and I tried to build it (Slackware 10.2 with default GCC 3.3.6). However, the build process fails each time it reaches lib/Target/XXX/XXXISelDAGToDAG.cpp for all backends (XXX=X86, ARM, ...), e.g. like: /.../llvm-build/lib/Target/ARM/ARMGenDAGISel.inc:145: error: syntax error before `{' token ... [lots of other errors generated by the previous one] /.../llvm-build/lib/Target/ARM/ARMGenDAGISel.inc:191: error: syntax error before `{...

...nly assert some of the time, as the inputs are not changing. Could it be a problem with my system itself, or perhaps I'm running low on RAM? If anybody has any insight on how to troubleshoot this kind of problem, i'd be very grateful. Also, I have not overriden runOnMachineFunction() in my XXXISelDagToDag.cpp file, so this is happening somewhat out of my control. Should I attempt to override it? I noticed that only a couple targets actually override runOnMachineFunction() for that particular pass (MIPS, I think is one). Sincerely, ~MathOnNapkins / Dave -------------- next part -------------- An HTM...

...running under valgrind. Ciao, Duncan. Could it be > a problem with my system itself, or perhaps I'm running low on RAM? If anybody > has any insight on how to troubleshoot this kind of problem, i'd be very grateful. > > Also, I have not overriden runOnMachineFunction() in my XXXISelDagToDag.cpp > file, so this is happening somewhat out of my control. Should I attempt to > override it? I noticed that only a couple targets actually override > runOnMachineFunction() for that particular pass (MIPS, I think is one). > > Sincerely, > ~MathOnNapkins / Dave > > > &g...

...it be > >> a problem with my system itself, or perhaps I'm running low on RAM? If >> anybody >> has any insight on how to troubleshoot this kind of problem, i'd be very >> grateful. >> >> Also, I have not overriden runOnMachineFunction() in my >> XXXISelDagToDag.cpp >> file, so this is happening somewhat out of my control. Should I attempt to >> override it? I noticed that only a couple targets actually override >> runOnMachineFunction() for that particular pass (MIPS, I think is one). >> >> Sincerely, >> ~MathOnNapkins...

...oblem with my system itself, or perhaps I'm running low on RAM? If >>> anybody >>> has any insight on how to troubleshoot this kind of problem, i'd be very >>> grateful. >>> >>> Also, I have not overriden runOnMachineFunction() in my >>> XXXISelDagToDag.cpp >>> file, so this is happening somewhat out of my control. Should I attempt >>> to >>> override it? I noticed that only a couple targets actually override >>> runOnMachineFunction() for that particular pass (MIPS, I think is one). >>> >>> Si...

On Aug 9, 2006, at 06:17, Bram Adams wrote: > Today I downloaded LLVM 1.8 (until yesterday I used 1.7) and I > tried to build it (Slackware 10.2 with default GCC 3.3.6). However, > the build process fails each time it reaches lib/Target/XXX/ > XXXISelDAGToDAG.cpp for all backends (XXX=X86, ARM, ...) > > The NOINLINE-macro after each method's argument list and right > before the "{" in the various lib/Target/XXX/XXXGenDAGISel.inc- > files seems to be the culprit, e.g. in llvm-build/lib/Target/ARM/ > ARMGenDAGISel.inc (lin...