search for: langreg

...vm releases, encoded debug info representation in llvm IR has changed only once (using metadata, instead of global variables). All other changes are incremental *and* backward compatible. Regarding documentation, it is on my list. However, your argument has same disconnect as some one who looks at LangReg and says I do not know what exactly FE has to generate to produce a working program. Well, what you need is a How To Write a Front End document. > 2. Enhance Validate() methods to be extremely strict (like Module's), > so it fails straight away See my response regarding Verify(). >...

On 17 March 2011 06:40, Talin <viridia at gmail.com> wrote: > The code that generates debugging information is quite fragile - you have to > generate metadata for each of your files, classes, and functions, and do so > without error, because if you do make a mistake, the only way you'll find > out is because gdb refuses to debug your program. And as I work on the code, >

...s and everything went back to normal again. So, while the infrastructure actually worked in the end, it took me by surprise and I had to guess what was going on to fix it properly. > Regarding documentation, it is on my list. However, your argument has same disconnect as some one who looks at LangReg and says I do not know what exactly FE has to generate to produce a working program. Well, what you need is a How To Write a Front End document. The debug documentation is not up-to-date. Metadata generated by DIBuilder doesn't look like what's in the docs. And the document describes some...

One problem that has been vexing me of late: It seems that whenever I run into a problem that requires debugging one of my programs in gdb, before I can do that I have to fix my frontend's broken generation of debugging info. The code that generates debugging information is quite fragile - you have to generate metadata for each of your files, classes, and functions, and do so without error,