[libc] Add `IN6_IS_ADDR_{LINK, SITE}LOCAL` (#168207)
This patch introduces two macros in `netinet/in.h`. The redundant tests
for macro values in the testcases have been removed.
[AMDGPU] Hoist s_set_vgpr_msb past SALU program state instructions (#172108)
Hoisting past the program state instructions is legal and allows for
better coissue.
Revert "[lldb/test] Enable debug info for TestFrameProviderCircularDependency.py"
This reverts commit 13b4eb9452d37106b1143723e658010a9b58d344 since it
doesn't fix the test failure.
Signed-off-by: Med Ismail Bennani <ismail at bennani.ma>
[libc] Properly fix printf long double subnormals (#172103)
In a previous PR I fixed one case where subnormal long doubles would
cause an infinite loop in printf. It was an improper fix though. The
problem was that a shift on the fixed point representation would
sometimes go negative, since the effective exponent of a subnormal is
lower than the minimum allowed exponent value. This patch extends the
fixed point representation to have space for subnormals, and adds an
assert to check that lshifts are always positive. The previous fix of
sometimes shifting right instead of left caused a loss of precision
which also sometimes caused infinite loops in the %e code.
[clang][DependencyScanning] Move driver-command logic for by-name scanning into DependencyScanningTool (#171238)
This is the second patch in a series that removes the dependency of
clangDependencyScanning on clangDriver, splitting the work from
#169964 into smaller changes (see comment linked below).
This patch updates the by-name scanning interface in
DependencyScanningWorker to accept only -cc1 command lines directly
and moves the logic for handling driver-style command lines into
DependencyScanningTool in clangTooling.
Support for -cc1 command lines in by-name scanning is introduced in
this patch.
The next patch will update the remaining parts of
DependencyScanningWorker to operate only on -cc1 command lines,
allowing its dependency on clangDriver to be removed.
https://github.com/llvm/llvm-project/pull/169964#pullrequestreview-3545879529
[lldb] Still echo the command if we print the error. (#171931)
When the command interpreter is asked to not echo commands but still
print errors, a user has no idea what command caused the error.
For example, when I add `bogus` in my `~/.lldbinit`:
```
$ lldb
error: 'bogus' is not a valid command.
```
Things are even more confusing when we have inline diagnostics, which
point to nothing. For example, when I add `settings set target.run-args
-foo` to my `~/.lldbinit`:
```
❯ lldb
˄˜˜˜
[6 lines not shown]
[acc][test] add tests for RegionBranchOpInterface for acc regions (#172073)
use last modified analysis to test if RegionBranchOpInterface is correct
on acc regions
