[lldb-dev] Process for making LLVM changes?
daniel.malea at intel.com
Thu Jul 25 12:50:46 PDT 2013
Hi Richard, welcome!
LLDB is not pinned to any specific LLVM/Clang revision (anymore) -- It's recommended to stay at (or around) trunk for all repos.
If you have patches with dependencies on other patches, just be explicit about the dependency when you post them for review. When they get committed, the dependency just has to be observed.
If your patches are non-trivial, you can make them easier to review (and test) by posting them on llvm-reviews.chandlerc.com! If you use that tool posting to the list can be streamlined by adding the mailing list (lldb-commits or llvm-commits) to the CC field when you submit the review request.
From: Richard Mitton <richard at codersnotes.com<mailto:richard at codersnotes.com>>
Date: Thursday, 25 July, 2013 3:28 PM
To: "lldb-dev at cs.uiuc.edu<mailto:lldb-dev at cs.uiuc.edu>" <lldb-dev at cs.uiuc.edu<mailto:lldb-dev at cs.uiuc.edu>>
Subject: [lldb-dev] Process for making LLVM changes?
I have a lldb patch I'm working on that requires changes to the LLVM code. I was wondering what the general procedure is for doing stuff like this; do I just submit my changes to the LLVM mainline first, and then submit an lldb patch? I don't want to be in a situation where lldb has a patch approved but it got rejected from LLVM...
Is lldb tied to a specific LLVM revision or are developers generally expected to have latest?
richard at codersnotes.com<mailto:richard at codersnotes.com>
More information about the lldb-dev