macho-dump deprecation/removal plan

[Alex Rosenberg via llvm-commits]

I'm happy to reduce the number of tools that reimplement the same concepts when possible. Many thanks for taking this on!

I do have some reservations about some of the rewritten tests that now use llvm-readobj. Most notably, the CHECK lines are now checking that the dump has not only the correct byte values, but also that the character representation of those byte values renders the same as well. For example, the SectionData elements in r247235. Nothing major to worry about, but I can picture a day where we obey locale differently or something and the rendering changes.

Alex

On Sep 9, 2015, at 6:59 PM, Davide Italiano via llvm-commits <llvm-commits at lists.llvm.org> wrote:

> Hi,
> in the last month I spent some time implementing the missing MachO
> specific features in llvm-readobj, and converting all the remaining
> tests that used macho-dump to the new format.
> llvm-readobj should have all the functionality that macho-dump had. If
> there's something missing, please open a bug and assign to me, I'll
> try to do my best to fill the gap.
> 
> That said, I would like to get rid of macho-dump in the near future.
> If there are objections, please raise them. If there are not, I would
> like to get rid of macho-dump in 1 week time from now. If this seems
> to aggressive, please propose a better schedule.
> 
> Thanks,
> 
> -- 
> Davide
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits