[lld] [LLD][COFF] Add -build-id flag to generate .buildid section. (PR #71433)

[Martin Storsjö via llvm-commits]

================
@@ -389,3 +389,13 @@ Test GCC specific LTO options that GCC passes unconditionally, that we ignore.
 
 RUN: ld.lld -### foo.o -m i386pep -plugin /usr/lib/gcc/x86_64-w64-mingw32/10-posix/liblto_plugin.so -plugin-opt=/usr/lib/gcc/x86_64-w64-mingw32/10-posix/lto-wrapper -plugin-opt=-fresolution=/tmp/ccM9d4fP.res -plugin-opt=-pass-through=-lmingw32 2> /dev/null
 RUN: ld.lld -### foo.o -m i386pep -plugin C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/liblto_plugin.dll -plugin-opt=C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/lto-wrapper.exe -plugin-opt=-fresolution=C:/msys64/tmp/cckbC7wB.res -plugin-opt=-pass-through=-lmingw32 2> /dev/null
+
+RUN: ld.lld -### foo.o -m i386pep 2>&1 | FileCheck -check-prefix=BUILD_ID %s
+RUN: ld.lld -### foo.o -m i386pep --build-id 2>&1 | FileCheck -check-prefix=BUILD_ID %s
+BUILD_ID:-build-id
----------------
mstorsjo wrote:

Hmm; technically, when matching for `-build-id`, it will also match if the output was `-build-id:no`. Not sure if it's best to have a `-NOT` pattern here, or do something like `-build-id{{ }}` to force there to be a space after it (as I presume we're not at the end of the line here)?

Nit: Space after `:`

https://github.com/llvm/llvm-project/pull/71433