I don't strictly needed, but this matches how MSVC lib.exe writes to archives, so this makes llvm-lib more compatible and simplifies comparing output between tools.
Details
Diff Detail
Unit Tests
Event Timeline
Not sure if I have a strong opinion on whether we should do this... but I guess this is reasonable.
llvm/lib/ToolDrivers/llvm-lib/LibDriver.cpp | ||
---|---|---|
142 | llvm::reverse. |
llvm/lib/ToolDrivers/llvm-lib/LibDriver.cpp | ||
---|---|---|
143 | Do we have a test covering the order of these printed filenames? It's surprising to me that we need to reverse here, but if it matches msvc it sounds good to me. |
Yes, it's covered by tests, llvm-lib/list.test and two other tests fail if I'd change the order written to the archive, but don't change printed order. I also manually confirmed that with VS 2022.
@jacek If you don't have commit access, I can push the patch for you - what's your preferred git author line for these patches?
Yes, I don't have commit access. Please use "Jacek Caban <jacek@codeweavers.com>". Thanks!
llvm::reverse.