Open int3 opened 3 years ago
Umbrella task for all known-incomplete LLD features related to debug info handling / STABS generation.
I intended this as a task description, not a reply. Sorry, still getting used to this bug tracker...
Umbrella task for all known-incomplete LLD features related to debug info handling / STABS generation.
If all its dependencies are fixed. Is it not common to create master/tracking task for larger features?
Ish - usually there's a bit more detail about what the broader feature is. What bugs would or would not fall under this master bug to determine when it's complete (or at least what to expect to find or not find here, etc - I think we do have some tracking bugs that likely will never close, more as groupings - eg: optimized debug info).
Is there some level of functionality that would be "enough" (presumably there will always be more bugs in Mach-O LLD (as there will be in any software) but some level of functionality, some overall test case(s) that will be considered adequate for this bug to be considered fixed) for this issue?
& yeah, probably including LLD and Mach-O in the title would help too, thanks!
Also, to be clear, this is specifically for LLD for Mach-O (hence the product and component this is filed under). Would it help if the title also reflected that?
I realize I put the dependencies into the blocking list. Whoops.
If all its dependencies are fixed. Is it not common to create master/tracking task for larger features?
This bug is a bit vaguely named - what criteria would be met that would cause this bug to be marked as fixed?
assigned to @alexshap
Extended Description
Hi-Pris: llvm/llvm-project#48058 llvm/llvm-project#48626 Mid-Pri: llvm/llvm-project#48729 (used by Swift) Low-Pris: llvm/llvm-project#47981