yes: Completely overengineer
If we're going to overengineer this, we may as well go all the way.
* If multiple arguments are given, concatenate them into a space-
separated list like GNU coreutils does.
* When duplicating the expletive, do so exponentially.
* Most importantly, don't modify the memory that argv points to.
MFC after: 1 week
Sponsored by: Klara, Inc.
Reviewed by: kevans, allanjude
Differential Revision: https://reviews.freebsd.org/D55617
net-mgmt/telegraf: Upgrade to 1.38.0
Change the rc script to require login, since some custom setups would
expect random services to be up and running and available for
monitoring.
Release notes: https://github.com/influxdata/telegraf/releases/tag/v1.38.0
[X86] Enable i256 fshl/fshr lowering on avx512 targets (#185455)
If freely foldable to vector, concat the i256 halves as v4i64 -> v8i64 and use the existing i512 shift lowering
Part of #184828
[LangRef] Specify semantics for non-byte-sized loads and stores (#180739)
LangRef currently specifies that non-byte-sized stores write an
unspecified bit pattern in the "padding", and that performing a
subsequent load with a different bitwidth is "undefined". This means
that storing an i1 value and then loading it as i8, the result is
"undefined" (whatever that is supposed to mean). These semantics are
quite unusual as they depend on the exact type a memory location has
been accessed with previously. I believe that frontends often do not
respect these semantics.
This PR proposes to instead specify that non-byte-sized loads
effectively act like like a byte sized `load` followed by `trunc nuw`,
and non-byte-sized stores act like a `zext` followed by a byte-sized
store. To the best of my knowledge, this matches the legalization
behavior of SDAG.
This does restrict possible codegen choices (e.g. a target couldn't
define these as `sext`/`trunc nsw` instead anymore), but it does not
appear that there is any interest in that in practice, given that SDAG
does not support it to this day.
[libc++] Drop the unrepresentative search_n benchmark (#184783)
This benchmark isn't very good at benchmarking `search_n`, since a good
`search_n` implementation can go through it in ~10 perfectly predictable
steps. We can drop it to avoid spending unnecessary resources. This also
fixes that the two benchmark sets have identical names.
Fixes #183832
www/firefox-esr: add some missing unveils
- content process already accesses /etc/localtime, add /usr/share/zoneinfo
- main process already has /usr/share/zoneinfo, add /etc/localtime
- main process sometimes parses /etc/hosts (mostly on network.trr.mode
changes ?) so unveil it.
- unveil.socket is wrong but time is running out, and the socket process
isnt used much anyway (network.http.network_access_on_socket_process.enabled defaults to false)
required by upcoming changes to pledge/unveil
www/mozilla-firefox: add some missing unveils
- content process already accesses /etc/localtime, add /usr/share/zoneinfo
- main process already has /usr/share/zoneinfo, add /etc/localtime
- main process sometimes parses /etc/hosts (mostly on network.trr.mode
changes ?) so unveil it.
- unveil.socket is wrong but time is running out, and the socket process
isnt used much anyway (network.http.network_access_on_socket_process.enabled defaults to false)
required by upcoming changes to pledge/unveil
[LifetimeSafety] Handle escape through assignment to global storage (#181646)
This PR allows for modelling escape of parameters to global storage, and
dangling global storage.
Change summary:
1. Created `GlobalEscapeFact` as a subclass of `OriginEscapesFact`
2. Emit a `GlobalEscapeFact` for all origins with global-storage that
remain live at function exit.
3. Integrated into warning reporting as necessary, introducing the
groups `-Wlifetime-safety-dangling-global` and
`-Wlifetime-safety-dangling-global-moved`
4. Wrote sema tests for escape to a variety of global storage locations.
