search for: beginassembly

...map is not printed at all. Is this a known issue or I 'm doing something wrong? I used a custom GCMetadataPrinter plugin but I reproduced this using the builtin "ocaml" GC plugin and the attached file (actually, any simple ll file that uses "ocaml" gc is fine). Note: The beginAssembly function works great. Best wishes, yiannis -- Yiannis Tsiouris Ph.D. student, Software Engineering Laboratory, National Technical University of Athens WWW: http://www.softlab.ntua.gr/~gtsiour -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: g...

...Is this a known issue or I 'm doing something wrong? > > I used a custom GCMetadataPrinter plugin but I reproduced this using the > builtin "ocaml" GC plugin and the attached file (actually, any simple ll > file that uses "ocaml" gc is fine). > > Note: The beginAssembly function works great. > I've tried adding two debug prints in lib/CodeGen/AsmPrinter/OcamlGCPrinter.cpp: one in beginAssembly and one in finishAssembly. It seems to me that finishAssembly is never called. Has anyone tried anything similar? Testing this should be rather straightforwar...

Hi all, In order to support linking AsmWriter separately from CodeGen, the Collector class (a CodeGen component) had to be decoupled from the AsmWriter interface. This required moving the beginAssembly and endAssembly methods to a separate abstract base class. If you had overridden these methods, your class may compile successfully but fail at runtime with a message of the form: no GCMetadataPrinter registered for collector: %s The fix is to transition your overrides to a subclass of...

I updated my from LLVM 2.7 to 2.8/trunk tonight and was mystified as to why my GC plugin silently stopped working. The problem was that the signature of the virtual function GCMetadataPrinter::finishAssembly (and beginAssembly) changed. This change would probably be an excellent candidate for the "gotchas" section of the 2.8 release notes. Thanks! -- Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100911/70559a74/at...

...r I 'm doing something wrong? >> >> I used a custom GCMetadataPrinter plugin but I reproduced this using the >> builtin "ocaml" GC plugin and the attached file (actually, any simple ll >> file that uses "ocaml" gc is fine). >> >> Note: The beginAssembly function works great. > I've tried adding two debug prints in > lib/CodeGen/AsmPrinter/OcamlGCPrinter.cpp: one in beginAssembly and > one in finishAssembly. It seems to me that finishAssembly is never > called. I used git bisect and I think the commit that is responsible for thi...

Hi Ben, > I updated my from LLVM 2.7 to 2.8/trunk tonight and was mystified as to why my > GC plugin silently stopped working. > > The problem was that the signature of the virtual function > GCMetadataPrinter::finishAssembly (and beginAssembly) changed. > > This change would probably be an excellent candidate for the "gotchas" section > of the 2.8 release notes. can you please send some text appropriate for the release notes that explains the problem. Thanks a lot, Duncan.

...wrong? >>> >>> I used a custom GCMetadataPrinter plugin but I reproduced this using the >>> builtin "ocaml" GC plugin and the attached file (actually, any simple ll >>> file that uses "ocaml" gc is fine). >>> >>> Note: The beginAssembly function works great. >> I've tried adding two debug prints in lib/CodeGen/AsmPrinter/OcamlGCPrinter.cpp: one in beginAssembly and one in finishAssembly. It seems to me that finishAssembly is never called. > > I used git bisect and I think the commit that is responsible for this is...

...r> wrote: > Hi Ben, > > > I updated my from LLVM 2.7 to 2.8/trunk tonight and was mystified as to > why my > > GC plugin silently stopped working. > > > > The problem was that the signature of the virtual function > > GCMetadataPrinter::finishAssembly (and beginAssembly) changed. > > > > This change would probably be an excellent candidate for the "gotchas" > section > > of the 2.8 release notes. > > can you please send some text appropriate for the release notes that > explains > the problem. > > Thanks a lot, >...