[DirectX] Move IR printing to DXILPrettyPrinter (#198318)
By doing the IR printing inside DXILPrettyPrinter, we have the option to
customise what we print and include the info that we collect and
generate in DXILDebugInfo.
Revert "[LSR] Narrow search space by merging users outside and inside loop" (#201581)
This is causing buildbot failures.
Reverts llvm/llvm-project#185929
www/privoxy: Update 4.1.0 => 4.2.0
Privoxy 4.2.0 fixes a couple of bugs and brings general improvements
such as support for elliptic-curve keys.
Two potential security problems have been reported and addressed.
Changelog:
https://lists.privoxy.org/pipermail/privoxy-announce/2026-June/000013.html
Port changes:
- The Privoxy tools come with proper man pages now so install
them when the tools are enabled.
PR: 295848
Reported by: Fabian Keil <fk at fabiankeil.de> (maintainer)
Approved by: osa, vvd (Mentors, implicit)
MFH: 2026Q2
(cherry picked from commit c9cc3d36733d5f4f0ce5ae4f6b3ce02ca868384c)
www/privoxy: Update 4.1.0 => 4.2.0
Privoxy 4.2.0 fixes a couple of bugs and brings general improvements
such as support for elliptic-curve keys.
Two potential security problems have been reported and addressed.
Changelog:
https://lists.privoxy.org/pipermail/privoxy-announce/2026-June/000013.html
Port changes:
- The Privoxy tools come with proper man pages now so install
them when the tools are enabled.
PR: 295848
Reported by: Fabian Keil <fk at fabiankeil.de> (maintainer)
Approved by: osa, vvd (Mentors, implicit)
MFH: 2026Q2
Fix clang/test/DebugInfo/CXX/line.cpp (#198401)
This PR twaeks the clang/test/DebugInfo/line.cpp test to pass on z/OS.
The reason the test was failing is that the RUN lines which specify
-triple %itanium_abi_triple expands to s390x-ibm-zos when run on z/OS.
The IR that is emitted for this triple does not match the patterns
expected by the test.
This PR tweaks the patterns in the CHECK lines so that the test also
passes on z/OS.
[BOLT] Add pre-parsed perf script support (#163785)
Implement the functionality to read and parse a pre-parsed perf-script
profile generated by perf2bolt's '--profile-format=perfscript' option.
The '-ps' option defines the perfscript input profile format. It requires
specifying the aggregation type ('--spe', '--ba') if it differs from
the default one ('brstack'). Note that the profile has to also be generated
using the exact same aggregation type.
Examples:
For ARM SPE:
1) $ perf2bolt BINARY -p perf.data -o test.text --spe --profile-format=perfscript
2) $ perf2bolt BINARY -o test.fdata -p test.text --spe -ps
For Brstack aggregation:
1) $ perf2bolt BINARY -p perf.data -o test.text --profile-format=perfscript
2) $ perf2bolt BINARY -o test.fdata -p test.text -ps
games/falconseye: fix build with llvm22
pretty much the same diff as for as games/slash:
- disable BSD code paths using long time_t
- disable setrandom()
apparently game saving is currently broken.
from maintainer espie + regen plist and wantlib
[z/OS] Modify regex in error message to match on z/OS. (#194020)
This PR modifies regex in error message to match on z/OS:
```
[Errno 129] EDC5129I No such file or directory.: 'temp1.txt'
wc: file "missing-file": EDC5129I No such file or directory.
cat: does-not-exist: EDC5129I No such file or directory.
```
[clang-repl] Fix Value::setRawBits unit confusion and right-size raw storage. (#200886)
Value::setRawBits had inconsistent units: the default value and the size
assert treated the parameter as bytes (sizeof(Storage)), while the
memcpy treated it as bits (NBits / 8). A caller passing the natural byte
count (e.g. sizeof(long long)) ended up copying only sizeof(T)/8 bytes
-- one byte for an 8-byte payload, leaving the rest stale. The one
in-tree caller compensated by multiplying by 8, hiding the bug.
Rename the parameter to NBytes and drop the / 8 so the API name,
default, assert, and memcpy all agree on bytes. Update the caller in
InterpreterValuePrinter.cpp to pass ElemSize directly.
Right-size the Storage::m_RawBits array while we are here: it was
sizeof(long double) * 8 bytes, which reads like a bit/byte confusion
since the widest typed member of the union is long double itself. The
oversized array made sizeof(Value) ~144 bytes on x86_64 instead of ~40,
bloating every copy/move of a Value.
[3 lines not shown]
[Offload][libomptarget] Replace slow `omp_target_memset` implementation by `dataFill` (#200202)
`omp_target_memset` was initially implemented before the existance of
`offload`. Because of this, a slow path was chosen to implement
`omp_target_memset`, first allocating memory on the host, calling
`memset` on that memory, and then transferring this to the device.
Aside from the inefficient way of setting device memory, this also
causes a data transfer event for the OpenMP Tools Interface, interfering
with the added memset event in OpenMP v6.0.
Since offload implements setting data via `dataFill` by now, replace the
slow path by just calling `dataFill` instead. This resolves both the
inefficiency, and removes the superfluous event dispatched to a tool.
Signed-off-by: Jan André Reuter <j.reuter at fz-juelich.de>
libarchive: Clean up the build configuration
* Move settings duplicated in libarchive, bsdcat, bsdcpio, bsdtar, and
bsdunzip into libarchive's Makefile.inc.
* Drop some CFLAGS that merely duplicated some of the contents of our
platform configuration header.
MFC after: 1 week
Reviewed by: mm
Differential Revision: https://reviews.freebsd.org/D57307
games/slash-em: fix build with llvm22
Replace one weird spelling of NULL with another one that doesn't break
the compilation.
from maintainer espie + regen plist and wantlib
