(math/R-Deriv) Updated 4.1.6 to 4.2.0
Version 4.2.0
=============
* 2025-06-20
- added `with()` construct
- fixed as.integer() for big numbers in simplification of fractions (fixing issue #29)
(math/R-DBI) Updated 1.2.3 to 1.3.0
# DBI 1.3.0 (2026-02-11)
## Features
- Add support for OpenTelemetry via the otel and otelsdk packages
(@shikokuchuo, #551).
## Bug fixes
- `dbWithTransaction()` calls `dbRollback()` also on interrupt
(@klin333, #528).
- `dbQuoteLiteral()` uses the format `"%Y-%m-%d %H:%M:%S%z"` which is
understood by more databases (#486).
## Documentation
[21 lines not shown]
(math/R-RNetCDF) Updated 2.9.2 to 2.11.1
Version 2.11-1, 2025-04-30
* Do not use nc-config compiler by default
* Use new R API functions for environments
* Use config.h to simplify compiler flags
* Call gc before opening datasets
- This may avoid corruption or crashes if a dataset is changed
unexpectedly when the garbage collector closes unreferenced ncids
Version 2.10-2, 2025-04-15
* Fix bashism in configure.ac
Version 2.10-1, 2025-04-13
* Detect and work around broken nc-config in configure script
- Try static option with nc-config if linking fails without it
- Use compiler from nc-config which may enable MPI
- Try pkg-config if nc-config fails or is disabled
* Prepare for upcoming change to bit64 package namespace
* Remove call to non-API entry point in R
[NFC][LLVM] Refactor IIT_ANY payload for vector/element constraint (#203506)
Change `IIT_ANY` payload from a single packed OverloadIndex + AnyKind
byte to 2 bytes:
- An 8 bit OverloadIndex
- An 8 pit packed vector + element type constraint.
This will enable `IIT_ANY` to express constraints on the overload type
is a more general fashion compared to a flat `AnyKind` enum.
Also fixed a latent bug in fixed encodings generated by the intrinsic
emitter (exposed by this change). Existing `encodePacked` packs the
type-signature as 8 nibbles into a 32-bit word and then checks if the
MSB bit position (i.e., bit 15) is 0 (to allow it's use in fixed
encoding). This effectively drop any 0 valued bytes in the encoding in
the upper 4 nibbles. Fix this by changing `encodePacked` to use the
actual fixed encoding type and its size.
fusefs: only search for FREAD fufh in readdir
The extra search for an FEXEC fufh shall be removed, since readdir
is only supposed to be called on a directory opened with FREAD. The
sole exception is NFS, which will call VOP_READDIR with directories that
aren't open at all. fuse already has special code to handle that.
Also remove the fuse_filehandle_get_dir() function, since it's not
used anywhere else.
Signed-off-by: CismonX <admin at cismon.net>
Reviewed by: asomers
MFC after: 2 weeks
Pull Request: https://github.com/freebsd/freebsd-src/pull/1729
[flang][CUDA] Keep host literals from using unified-memory generic distance (#201257)
Fix CUDA generic resolution under `-gpu=mem:unified` so unattributed
literals and expression temporaries are not treated as unified-memory
actuals.
Previously, a host scalar literal such as `1.0` could score as
compatible with a `DEVICE` dummy and incorrectly select the
device-scalar overload. This could pass a host stack address to a device
helper and fail at runtime. The fix applies the unified/managed memory
distance columns only to symbol-backed actuals.
(textproc/R-readr) Updated 2.1.5 to 2.2.0
# readr 2.2.0
-------------
This release advances many deprecations.
* `melt_csv()`, `melt_csv2()`, `melt_delim()`, `melt_tsv()`,
`melt_fwf()`, `melt_table()`, `melt_table2()`, and all
`melt_*_chunked()` variants have been removed from readr. These
functions were deprecated in readr 2.0.0 (2021-07-20). See the meltr
package (https://github.com/r-lib/meltr).
* `read_table2()` has been removed from readr. This function was
deprecated in readr 2.0.0 (2021-07-20) in favor of
`read_table()`. Use `read_table()` instead.
* `read_csv()`, `read_csv2()`, `read_tsv()`, `read_delim()`, and
`read_fwf()` now emit a deprecation warning when literal data is
passed without wrapping it in `I()`. For example, usage like
[41 lines not shown]
[flang][cuda] Fix host loads from CUDA constant globals (#203064)
This fixes CUDA Fortran lowering for scalar module variables with the
constant attribute that are read from host code, such as launch
configuration expressions or CUF kernel loop bounds.
Previously, host-side declarations for these globals could be rewritten
to device constant-memory addresses, causing host loads to dereference
the result of _FortranACUFGetDeviceAddress. The fix preserves host reads
from the host-visible global while still using the device address for
host-to-device assignment updates.
A FIR regression test covers host reads and assignment updates for
scalar CUDA constant globals.
