[AMDGPU] Make direct f16 <-> i32 conversion illegal (#205565)
Neither SALU nor VALU support direct conversion from f16 to/from i32.
Previously, this was still legal and handled by instruction selection
patterns, forming chains f16 -> f32 -> i32 and i32 -> f32 -> f16 for the
two cases, respectively.
This change marks the conversion illegal and creates the same chains as
the pattern during (operation) legalization.
This had the added benefit that a combination of FNEG and FPTOSI/UI can
now merge the float negation into the source modifier of the f16-to-f32
conversion, as demonstrated by the GlobalISel tests.
This fixes https://github.com/llvm/llvm-project/issues/177342.
---------
Signed-off-by: Lukas Sommer <lukas.sommer at amd.com>
[lldb] Always lock in StreamLogHandler::Write (#205771)
This code assumes that writing to an unbuffered raw_fd_ostream from
multiple threads is somehow safe. raw_fd_ostream doesn't make any
guarantees about this from what I can see.
The current raw_fd_ostream implementation also uses a looping write call
to write the content in chunks, and doing this from multiple threads
leads to interleaving log messages.
This patch unconditionally make us aquire the stream lock.
rtld: Check for -1 as an-end-of-section marker
rtld calls functions in the .init_array section one at a time, until
it finds a distinguished sentinel value. The C runtime does the same
thing (in crtend.c). However, that checks for the sentinel -1 and not
1. If one is using a linker that unifies .ctors and .init_array, then
rtld will miss the sentinel value. I believe the author of this code
intended to write -1 instead of 1. Indeed, changing the code to also
check for -1 prevents rtld from attempting to call a non-existent
function. The same is true of .dtors and .fini_array.
Signed-off-by: Daniel Levin <daniellevin2607 at gmail.com>
Reviewed by: kib
MFC after: 3 days
Pull Request: https://github.com/freebsd/freebsd-src/pull/2270
(cherry picked from commit 45a0cb52d3d62f8caae420b93e4b8c76ae3bc766)
AMDGPU: Use module flags to control xnack and sramecc
This ensures these ABI details are encoded in the IR module
rather than depending on external state from command-line flags.
Previously, these were encoded as function-level subtarget features.
The code object output was a single target ID directive implied
by the global subtarget. The backend would previously check if a
function's subtarget feature mismatched the global subtarget. This
is avoided by making xnack and sramecc module-level properties from
the start. This also provides proper linker compatibility
enforcement, moving the error point earlier.
The old encoding was also an abuse of the subtarget feature system.
Subtarget features are a bitvector, and later features in the string
can override earlier ones. The old handling added a special case
where explicit settings were preserved: ordinarily +feature,-feature
should result in the feature being disabled, but +xnack,-xnack would
preserve the explicit "-xnack" state, which differs from the absence
of any xnack setting.
[25 lines not shown]
AMDGPU: Remove leftover test for old promote-alloca subtarget feature (#206014)
This feature was removed in a56993a694ed02775285b9fe0e23fce8346491c9.
The test used to have a pair testing the enabled and disabled case,
and there's no point leaving the enabled partner.
Don't bounce unless we're doing encrypted writes. Drivers for hardware
that doesn't support 64-bit DMA will take care of bouncing now.
ok deraadt@, jca@
[AMDGPU][NFC] Roundtrip gfx11_asm_vop3_from_vop2.s (#205825)
Removes the need for gfx11_dasm_vop3_from_vop2_hi.txt sitting
downstream.
Catches a problem with printing op_sel for the tied operands in
v_fmac_f16_e64.
filesystems/amazon-efs-utils: update to 3.1.3
And fix a bug in doubled path substitution regarding the configuration file
of amazon-efs-mount-watchdog
Sponsored by: Netflix
net-mgmt/netbox: Update to 4.6.3
* Remove no longer required workarounds for Python 3.11 compatibility.
* Also prune update instructions for NetBox releases older than 3.6
while I'm here.
Netbox 4.6 contains many bugfixes/enhancements and the following new
features:
* Virtual Machine Types
* Cable Bundles
* Rack Groups
* ETag Support for REST API
* Cursor-based Pagination for REST API
https://netbox.readthedocs.io/en/stable/release-notes/version-4.6/
MFH: No (feature release)
net-mgmt/netbox: Create Django 6.0 consumers
* Django 5.2 is currently the "default" version in the ports tree due
its long term support until April 2028. Thus ports that are assigned
to that version will exist until then.
The following ports are required to make the upgrade of
net-mgmt/netbox to the 4.6 release possible because it requires
Django 6.0.
All of the ports listed below were created on the basis of their
respective original ports:
- devel/py-dj60-django-rq
- devel/py-dj60-strawberry-graphql
- graphics/py-dj60-sorl-thumbnail
- www/py-dj60-channels
- www/py-dj60-django-auth-ldap
- www/py-dj60-django-choices-field
[18 lines not shown]
