committers-ports: add andy
Following up ziaee's pattern, and add andy's line.
I'm not sure whether the original commit bit creation date should be used,
and use commit bit re-activation date for now.
MFC after: 1 week
(cherry picked from commit 0d9b5db9fc652e79e4eb08a2f583e9b825a50b92)
committers-ports: add andy
Following up ziaee's pattern, and add andy's line.
I'm not sure whether the original commit bit creation date should be used,
and use commit bit re-activation date for now.
MFC after: 1 week
(cherry picked from commit 0d9b5db9fc652e79e4eb08a2f583e9b825a50b92)
committers-ports: add andy
Following up ziaee's pattern, and add andy's line.
I'm not sure whether the original commit bit creation date should be used,
and use commit bit re-activation date for now.
MFC after: 1 week
(cherry picked from commit 0d9b5db9fc652e79e4eb08a2f583e9b825a50b92)
hugo: Update to 0.156.0
upstream changes:
-----------------
v0.156.0
This release brings significant speedups of collections.Where and collections.Sort – but this is mostly a "spring cleaning" release, to make the API cleaner and simpler to understand/document.
Deprecated
* Site.AllPages is Deprecated
* Site.BuildDrafts is Deprecated
* Site.Languages is Deprecated
* Site.Data is deprecated, use hugo.Data
* Page.Sites and Site.Sites is Deprecated, use hugo.Sites
Removed
These have all been deprecated at least since v0.136.0 and any usage have been logged as an error for a long time:
Template functions
* data.GetCSV / getCSV (use resources.GetRemote)
* data.GetJSON / getJSON (use resources.GetRemote)
* crypto.FNV32a (use hash.FNV32a)
* resources.Babel (use js.Babel)
[54 lines not shown]
pkg_autoremove/force delete: Fix order
If package A depends on package B (on a binary or script for example), when
autoremove is called currently the order is (likely) by alphabetic.
This cause problems as if package A is removed first and package B needs a script
from package A it will fails to clean up correctly the system.
Since autoremove is considered as force internally simply remove the check so we will
process the removals in the correct order.
Sponsored by: Beckhoff Automation GmbH & Co. KG
[OpenMP][MLIR] Modify lowering OpenMP Dialect lowering to support attach mapping
This PR adjusts the LLVM-IR lowering to support the new attach map type that the runtime
uses to link data and pointer together, this swaps the mapping from the older
OMP_MAP_PTR_AND_OBJ map type in most cases and allows slightly more complicated ref_ptr/ptee
and attach semantics.
[Flang][OpenMP][Offload] Modify MapInfoFinalization to handle attach mapping and 6.1's ref_* and attach map keywords
This PR is one of four required to implement the attach mapping semantics in Flang, alongside the
ref_ptr/ref_ptee/ref_ptr_ptee map modifiers and the attach(always/never/auto) modifiers.
This PR is the MapInfoFinalization changes required to support these features, it mainly deals with
applying the correct attach map type and manipulating the descriptor types maps for base address
and descriptor so that when we specify ref_ptr/ref_ptee we emit one of the two maps and when we
emit ref_ptr_ptee we emit our usual default maps. In all cases we add the "glue" of an new
attach map except in cases where a user has provided attach never. In cases where we are
provided an always, we apply the always map type to our attach maps.
It's important to note the runtime has a toggle for the auto map behaviour, which will flip the
attach behaviour to the newer semantics or the older semantics for backwards compatability (outside
the purview of this PR but good to mention).
Revert "fortune: fix netstat tip"
This reverts commit 8e593a1f143203cace2e14bd6629a8ebdf9b47dc. I was
totally wrong, so just revert and get on with it.
Sponsored by: Netflix
Revert "fortune: fix netstat tip"
This reverts commit 8e593a1f143203cace2e14bd6629a8ebdf9b47dc. I was
totally wrong, so just revert and get on with it.
Sponsored by: Netflix
