search for: writeobject

...at least try...) on it, what would be the "roadmap" ? I assume, a MCJITStreamer is needed. And probably a JITObjectWriter (inherits from MCObjectWriter) and an associated TargetAsmBackend specific to the JIT (JITX86AsmBackend) ? What would be the chaining of calls ? The JITObjectWriter::WriteObject is called via the AsmPrinter::doFinalization. But how the AsmPrinter will be created ? What was on your mind on this subject ? Anyone has already begin to work on this ? Olivier. On Sat, Apr 10, 2010 at 10:56 PM, Rick Mann <rmann at latencyzero.com> wrote: > > On Apr 9, 2010, at 23...

...hat would be the "roadmap" ? > > I assume, a MCJITStreamer is needed. > And probably a JITObjectWriter (inherits from MCObjectWriter) and an associated TargetAsmBackend specific to the JIT (JITX86AsmBackend) ? > > What would be the chaining of calls ? The JITObjectWriter::WriteObject is called via the AsmPrinter::doFinalization. But how the AsmPrinter will be created ? I'm not sure the best path forward on this, Daniel may have an opinion. The two options are to implement a new mcstreamer, or to implement a new ".o file" in the assembler backend. Of the two, I...

.../ADT/SmallVector.h:364 #8 operator+= (this=0x806fae8, Asm=..., Layout=...) at /home/matt/src/llvm-2.8/include/llvm/ADT/SmallString.h:57 #9 (anonymous namespace)::ELFObjectWriterImpl::CreateMetadataSections ( this=0x806fae8, Asm=..., Layout=...) at ELFObjectWriter.cpp:821 #10 0xb785f09d in WriteObject (this=0x806fad0, Asm=..., Layout=...) at ELFObjectWriter.cpp:831 #11 llvm::ELFObjectWriter::WriteObject (this=0x806fad0, Asm=..., Layout=...) ---Type <return> to continue, or q <return> to quit--- at ELFObjectWriter.cpp:972 #12 0xb786c71a in llvm::MCAssembler::Finish (this=0x807...

Hi all, One of the reasons the Livermore Loops couldn't be vectorized is that it was using global structures to hold the arrays. Today, I'm investigating why is that so and how to fix it. My investigation brought me to LoopVectorizationLegality::canVectorizeMemory(): if (WriteObjects.count(*it)) { DEBUG(dbgs() << "LV: Found a possible read/write reorder:" << **it <<"\n"); return false; } In the first pass, it registers all underlying objects for writes, than it does it again for reads, if the value was...

...ot;roadmap" ? >> >> I assume, a MCJITStreamer is needed. >> And probably a JITObjectWriter (inherits from MCObjectWriter) and an associated TargetAsmBackend specific to the JIT (JITX86AsmBackend) ? >> >> What would be the chaining of calls ? The JITObjectWriter::WriteObject is called via the AsmPrinter::doFinalization. But how the AsmPrinter will be created ? > > I'm not sure the best path forward on this, Daniel may have an opinion. The two options are to implement a new mcstreamer, or to implement a new ".o file" in the assembler backend. Of t...

...One of the reasons the Livermore Loops couldn't be vectorized is that it was using global structures to hold the arrays. Today, I'm investigating why is that so and how to fix it. > > My investigation brought me to LoopVectorizationLegality::canVectorizeMemory(): > > if (WriteObjects.count(*it)) { > DEBUG(dbgs() << "LV: Found a possible read/write reorder:" > << **it <<"\n"); > return false; > } > > In the first pass, it registers all underlying objects for writes, than it does it again fo...

...> > >> I assume, a MCJITStreamer is needed. > >> And probably a JITObjectWriter (inherits from MCObjectWriter) and an > associated TargetAsmBackend specific to the JIT (JITX86AsmBackend) ? > >> > >> What would be the chaining of calls ? The JITObjectWriter::WriteObject > is called via the AsmPrinter::doFinalization. But how the AsmPrinter will be > created ? > > > > I'm not sure the best path forward on this, Daniel may have an opinion. > The two options are to implement a new mcstreamer, or to implement a new > ".o file" in...

On Apr 9, 2010, at 23:32:12, Chris Lattner wrote: > Several people have asked what the MC project is all about, and it is now getting to a point where it is pretty interesting and there are lots of potential projects for people who are interested. I wrote a big post about what it is here: > http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html Thanks for the post, Chris. It

Several people have asked what the MC project is all about, and it is now getting to a point where it is pretty interesting and there are lots of potential projects for people who are interested. I wrote a big post about what it is here: http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html Thoughts and comments welcome, -Chris

...sons the Livermore Loops couldn't be vectorized is that it was using global structures to hold the arrays. Today, I'm investigating why is that so and how to fix it. > > > > My investigation brought me to LoopVectorizationLegality::canVectorizeMemory(): > > > > if (WriteObjects.count(*it)) { > > DEBUG(dbgs() << "LV: Found a possible read/write reorder:" > > << **it <<"n"); > > return false; > > } > > > > In the first pass, it registers all underlying objects for writes, than it does it again for r...