[llvm-branch-commits] [lld] [clang] [llvm] [docs] Add release notes for Windows specific changes in 18.x (PR #80011)

2024-01-30 Thread via llvm-branch-commits
@@ -359,6 +371,8 @@ Changes to LLDB fields are present, however this is not always possible or entirely accurate. If in doubt, refer to the numerical value. +* On Windows, LLDB can now read the thread names. oltolm wrote: Yes, in the sense that if a threa

[llvm-branch-commits] [lld] [clang] [llvm] [docs] Add release notes for Windows specific changes in 18.x (PR #80011)

2024-01-30 Thread David Spickett via llvm-branch-commits
@@ -319,6 +319,18 @@ Changes to the LLVM tools * llvm-objcopy now supports ``--gap-fill`` and ``--pad-to`` options, for ELF input and binary output files only. +* llvm-rc and llvm-windres now accept file path references in ``.rc`` files + concatenated from multiple string l

[llvm-branch-commits] [lld] [clang] [llvm] [docs] Add release notes for Windows specific changes in 18.x (PR #80011)

2024-01-30 Thread David Spickett via llvm-branch-commits
@@ -41,9 +41,25 @@ COFF Improvements * Added support for ``--time-trace`` and associated ``--time-trace-granularity``. This generates a .json profile trace of the linker execution. +* Prefer library paths specified with ``-libpath:`` over the implicitly + detected toolchai