Debugging docs wrong?

!1 = metadata !{
  i32 524329, ;; Tag
  metadata !"MySource.cpp",
  metadata !"/Users/mine/sources",
  metadata !3 ;; Compile unit

!2 is the Compile Unit, right? !3 is also wrong.

Yes. Thanks for catching this.
Fixed r108246.

Most welcome. :wink:

Btw, the 2.6 debug information (referred from the blog) doesn't warn
users that it's deprecated, nor it links to the new info (in an
obvious manner, at least), that is completely different. That happens
with the release notes that haven't been released yet, I think it
should be the same for all deprecated/yet-to-be-released documents.

A header will suffice, a watermark would be nice. :wink:


Reclaim your digital rights, eliminate DRM, learn more at

Which blog post are you referring to? I can update it...


Hi Chris,

Don't worry, the link is correct. It's in the post about metadata,
linking to the pre-2.6 debug infrastructure (and how bad it was). :wink:

But after reading the whole new one, I found that both were only too
similar in general appearance and layout. It'd be easy to take one for
the other, especially for someone new to llvm and how it deals with
metadata today.

I was just mentioning that would be goo practice to have some kind of
watermark on all deprecated documents, and maybe even a link to the
newest copy. As you always have the main link to the current one and
make version links to the others, that wouldn't be too hard to do:

It may look obvious from the URL, but recently browsers are doing
their best to reduce and hide it from less technical eyes. Maybe
whenever you guys move from the main docs to "release/n.m" directory,
you could change the CSS/DHTML to make the adjustments without
re-writing every page.

Like this:


Reclaim your digital rights, eliminate DRM, learn more at