[DAG] Fix -Wunused-variable
A recently introduced local is only used in an assertion which means we
get -Wunused-variable in release+noasserts builds. Mark it
[[maybe_unused]] rather than inlinine the definition given there are
multiple uses within the assert.
clang: Remove unnecessary triple normalize in offloading job (#189435)
These should already have been normalized (and the device side
comes from code, which should have been trivially normalized to
start).
www/*chromium: revert upstream commit to fix file dialog behaviour
This change reverts the following commit which neuters the Enter
key in the file dialogs by not preselecting the active button by
default because of the following joke:
+// GTK_RESPONSE_ACCEPT as the default button, which should be avoided to prevent
+// an exploit where the user is instructed to hold Enter before the dialog
+// appears.
commit e93121e97478a41d529c8586a48b4ec34173f79a
Author: Tom Anderson <thomasanderson at chromium.org>
Date: Mon Jan 5 17:42:17 2026 -0800
[GTK] Don't preselect file dialog accept buttons
(cherry picked from commit a50101eb4b6190b94c85b7cc0a0745ff44678c16)
www/*chromium: revert upstream commit to fix file dialog behaviour
This change reverts the following commit which neuters the Enter
key in the file dialogs by not preselecting the active button by
default because of the following joke:
+// GTK_RESPONSE_ACCEPT as the default button, which should be avoided to prevent
+// an exploit where the user is instructed to hold Enter before the dialog
+// appears.
commit e93121e97478a41d529c8586a48b4ec34173f79a
Author: Tom Anderson <thomasanderson at chromium.org>
Date: Mon Jan 5 17:42:17 2026 -0800
[GTK] Don't preselect file dialog accept buttons
www/*chromium: revert upstream commit to fix file dialog behaviour
This change reverts the following commit which neuters the Enter
key in the file dialogs by not preselecting the active button by
default because of the following joke:
+// GTK_RESPONSE_ACCEPT as the default button, which should be avoided to prevent
+// an exploit where the user is instructed to hold Enter before the dialog
+// appears.
commit e93121e97478a41d529c8586a48b4ec34173f79a
Author: Tom Anderson <thomasanderson at chromium.org>
Date: Mon Jan 5 17:42:17 2026 -0800
[GTK] Don't preselect file dialog accept buttons
[NFC] [AMDGPU] Added 2 options to rewrite-agpr-copy-mfma for debugging.
amdgpu-disable-rewrite-agpr-copy-mfma and amdgpu-rewrite-agpr-copy-mfma-limit
were added.
[clang-doc] Integrate enum LIT tests (#187818)
Combine the two separate test files and have them feed from a common
source. This will be the way that tests are handled to prevent testing
divergence in the future.
[lldb-dap][windows] don't use the ConPTY in internalConsole mode (#186472)
In `internalConsole` mode (especially in VSCode), lldb-dap should not
use the ConPTY to read the process' output. This is because the
internalConsole is not a real terminal, there is no reason to use
terminal emulation, which will add arbitrary line returns to the output.
Instead, this patch introduces the `eLaunchFlagUsePipes` flag in
ProcessLaunchInfo which tells ProcessLaunchWindows to use regular pipes
instead of a ConPTY to get the stdin and stdout of the debuggee.
The result is that output which is supposed to be on a single line is
properly rendered.
---
The following example is when debugging a program through lldb-dap on
Windows. The program prints the numbers 0 through 999 on a single line.
[15 lines not shown]
[NFC] Remove unused-but-set global variables (#189315)
Remove four global variables that are set but never read to fix
-Wunused-but-set-global warnings:
- `MFMAChainLength` in AMDGPUIGroupLP.cpp
- `Wide` in llvm-objdump.cpp
- `SaveTemps` in ClangSYCLLinker.cpp
- `DeprecatedDriverCommand` in ClangScanDeps.cpp
Follow up to #178342
[llvm lib] Read/write non-power-of-two sized unsigned integers (3, 5, 6, 7 bytes) in DataExtractor and FileWriter (#189098)
This allows tools (like gsymutil) to pack data more efficiently into a
file.
clang: Remove unnecessary triple normalize in offloading job
These should already have been normalized (and the device side
comes from code, which should have been trivially normalized to
start).
