This is an archive of the discontinued LLVM Phabricator instance.

[Kaleidoscope] Fix DWARF function creation example
ClosedPublic

Authored by jzbrooks on Jul 20 2022, 6:32 PM.

Details

Summary

The full code listing was fixed in fdaeb0c647eb66763721a7fe74e0a36b007dcd75

Diff Detail

Event Timeline

jzbrooks created this revision.Jul 20 2022, 6:32 PM
Herald added a project: Restricted Project. · View Herald TranscriptJul 20 2022, 6:32 PM
jzbrooks requested review of this revision.Jul 20 2022, 6:32 PM
Herald added a project: Restricted Project. · View Herald TranscriptJul 20 2022, 6:32 PM

The Debian check failures appear unrelated to this change. Unless all code snippets outside of the full tutorial code listing are compiled somehow, it seems unlikely this change is documentation-only. I'd guess they aren't compiled since this wasn't addressed sooner. I'm happy to be wrong. I'm a little surprised that the development branch has breakages. Is that common?

dblaikie accepted this revision.Jul 24 2022, 11:52 PM

Looks good to me, thanks!

This revision is now accepted and ready to land.Jul 24 2022, 11:52 PM

Thanks @dblaikie. I don’t have commit access, can you land this patch for me? Please use “Justin Brooks justin@jzbrooks.com” to commit the change.

I also wonder if this change would be beneficial to land in other branches as well. I was working with LLVM 11 (going to update it soon, hopefully), so when I encountered the problem the full code listing wasn't addressed either. I had to read LLVM source to figure out how to fix the problem. I'm happy to do that, but I'm not sure if there's a process for such things or if it would be valuable.

This revision was landed with ongoing or failed builds.Jul 25 2022, 11:20 AM
This revision was automatically updated to reflect the committed changes.

Thanks @dblaikie. I don’t have commit access, can you land this patch for me? Please use “Justin Brooks justin@jzbrooks.com” to commit the change.

Sure, done!

I also wonder if this change would be beneficial to land in other branches as well. I was working with LLVM 11 (going to update it soon, hopefully), so when I encountered the problem the full code listing wasn't addressed either. I had to read LLVM source to figure out how to fix the problem. I'm happy to do that, but I'm not sure if there's a process for such things or if it would be valuable.

@tstellar - any thoughts on whether it's suitable/worthwhile to backport this documentation fix?

There are no more 14.x updates planned, so we aren't doing backports any more.