search for: asethia

Hi, I found that machine dead code elimination, does not respect the calling convention of alpha and eliminates r16, which was set correctly during code generation. I verified it with -print-after-all. Does anybody have a patch for this? On Wed, Jun 29, 2011 at 11:12 AM, Ankit Sethia <asethia at eecs.umich.edu>wrote: > Hi All, > > I am using llvm-2.9 to cross compile to alpha. I know that alpha is in > experimental stage, but i can not get even the "Hello World" program to run > on it. > > Here is what happens, the bitcode file for the hello world prog...

Hi All, I am using llvm-2.9 to cross compile to alpha. I know that alpha is in experimental stage, but i can not get even the "Hello World" program to run on it. Here is what happens, the bitcode file for the hello world program is as follow: ; ModuleID = 'hello.bc' target datalayout =

Hi, Can people suggest how this is solved for other ISAs? This happens only for Alpha and not for x86-64. The register 16 does not have any uses within that function, but is used inside puts. So Machine DCE thinks it is dead code. On Wed, Jun 29, 2011 at 4:20 PM, Ankit Sethia <asethia at eecs.umich.edu>wrote: > Hi, > > I found that machine dead code elimination, does not respect the calling > convention of alpha and eliminates r16, which was set correctly during code > generation. I verified it with -print-after-all. > Does anybody have a patch for this? &...

Hi All, I am trying to understand how a back-end generates code for a function that has variable number of arguments. I would also to like to know what changes do i have to do to the corresponding ISAs InstrInfo.td when a call to such a function is made? Any pointers or documentation in this regard is greatly appreciated. -- Ankit -------------- next part -------------- An HTML attachment

Hi, I configure llvm to generate code for alpha. I use a the following steps to generate code from the source files: 1) llvm-gcc -c main.c -emit-llvm main.bc 2) opt -load <library fo myPass> -myPass main.bc main.opt.bc 3) llc -march=alpha main.opt.bc -o main.S 4) alphaev67-unknown-linux-gnu-as main.S -o main.o Most of the files that i compile run just fine. Suddenly, i have hit on a file

Hi All, I changed the CFG of a big function using a pass that runs on a function, I am having trouble debugging it. Is there someway to dump a module to a file from inside gdb? I have access to the Module pointer. Let me know if anything else is needed. -- Ankit -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Nadev, The module is really big and i would like the dump to happen in a file instead of stdout. Is that possible? On Sat, Jun 25, 2011 at 3:37 PM, Rotem, Nadav <nadav.rotem at intel.com> wrote: > Ankit, **** > > ** ** > > From within GDB you can run the following command:**** > > “call m->dump()”**** > > This will print the module in the bitcode in a