[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
[LSR] Narrow search space by merging users outside and inside loop (#185929)
Loop Strength Reduce can give different (and worse) results for a loop
when it is followed by uses of variables used inside the loop. This is
because the uses outside the loop increase the size of the search space,
which can lead to using NarrowSearchSpaceByPickingWinnerRegs which often
discards the best solution.
Solve this by narrowing the search space by merging uses outside the
loop with uses inside the loop. This ignores the Kind and AccessTy of
the use which can mean that the cost may be inaccurate, but it will give
the same cost as if we had just ignored the uses outside of the loop.
games/minetestmapper: revert removal and update 20220221 → 20250408
Please do not remove ports abruptly. Instead, go through a proper
process of first documenting the breakage with unconditional BROKEN
and then scheduling the removal with DEPRECATED/EXPIRATION_DATE.
Pointyhat to: diizzy
Bust global permissions lock
This commit replaces our global permissions mutation lock with
a per-path one. In the default case for UI / API changes of
permissions, the job is recursive and locked to a particular
dataset, and API call is made against dataset mountpoints. This
means that we can loosen things up generally to allow greater
concurrency in permissions operations safely. In order to
foot-shoot, a user would have to go out of their way to create
permissions jobs that interact with each other and the impact
of the foot shooting is that the last mutation wins (no chance
of corruption).
graphics/tippecanoe: revert removal
Please do not remove ports abruptly. Instead, go through a proper
process of first documenting the breakage with unconditional BROKEN
and then scheduling the removal with DEPRECATED/EXPIRATION_DATE.
This reverts commit 4c9bd41bd6fe492b8796ff927d3443ae1f5e58a2.
Pointyhat to: diizzy
[Clang][HIP] Include `__clang_cuda_math_forward_declares.h` before `<cmath>`
This patch should fix the following error on windows: https://github.com/ggml-org/llama.cpp/issues/22570
In HIP, constexpr functions are treated as both __host__ and __device__.
A new version of the MS STL shipped with the build tools version
14.51.36231 has constexpr definitions for some cmath functions when the
compiler in use is Clang.
These definitions conflict with the __device__ declarations we provide
in the header wrappers.
There is a workaround for this: It is possible to overload constexpr
functions **that are defined in a system header** by declaring a __device__
version before.
By moving `__clang_cuda_math_forward_declares.h` before `<cmath>` is
included we're able to benefit from this behavour.
Pull up the following, requested by mrg in ticket #304:
external/mit/xorg-server/dist/ChangeLog up to 1.1.1.33
external/mit/xorg-server/dist/configure up to 1.26
external/mit/xorg-server/dist/configure.ac up to 1.28
external/mit/xorg-server/dist/meson.build up to 1.1.1.23
external/mit/xorg-server/dist/meson_options.txt up to 1.1.1.4
external/mit/xorg-server/dist/Xext/saver.c up to 1.6
external/mit/xorg-server/dist/Xext/sync.c up to 1.16
external/mit/xorg-server/dist/Xi/xipassivegrab.c up to 1.9
external/mit/xorg-server/dist/dix/dixfonts.c up to 1.9
external/mit/xorg-server/dist/glx/glxcmds.c up to 1.17
external/mit/xorg-server/dist/glx/glxcmdsswap.c up to 1.5
external/mit/xorg-server/dist/glx/single2.c up to 1.5
external/mit/xorg-server/dist/glx/single2swap.c up to 1.5
external/mit/xorg-server/dist/hw/xfree86/dri2/dri2.c up to 1.7
external/mit/xorg-server/dist/include/closestr.h up to 1.1.1.5
external/mit/xorg-server/dist/miext/sync/misync.c up to 1.1.1.6
external/mit/xorg-server/dist/present/present_notify.c up to 1.1.1.4
[9 lines not shown]
[clang][bytecode] Fix a diagnostic difference with extern variables (#201369)
If the extern variable is constexpr of of non-array type, we should
diagnose it as missing an initializer. Otherwise, we diagose a read of
non-constexpr variable.
[FunctionAttrs] Switch readonly etc inference to use CaptureTracking (#201136)
Inference of memory attributes on arguments also needs to reason about
indirect accesses via captures and implemented a home-grown variant of
CaptureTracking for that purpose. Switch it to the shared
implementation, which slightly improves precision.
[Clang][HIP] Include `__clang_cuda_math_forward_declares.h` before `<cmath>`
This patch should fix the following error on windows: https://github.com/ggml-org/llama.cpp/issues/22570
In HIP, constexpr functions are treated as both __host__ and __device__.
A new version of the MS STL shipped with the build tools version
14.51.36231 has constexpr definitions for some cmath functions when the
compiler in use is Clang.
These definitions conflict with the __device__ declarations we provide
in the header wrappers.
There is a workaround for this: It is possible to overload constexpr
functions **that are defined in a system header** by declaring a __device__
version before.
By moving `__clang_cuda_math_forward_declares.h` before `<cmath>` is
included we're able to benefit from this behavour.
clang: Remove hacky OpenMP handling for appending bound arch (#201555)
Use the same path as CUDA/HIP and stop doing a hacky search through
the arguments looking for -march.