-
**Describe the bug**
A clear and concise description of what the bug is.
GUI apps worked fine, but windows 3.x console apps like the compiler in MSVC 1.52c doesn't work. It just say unsupported 16…
-
When I try pushing the model to a Hugging Face repo, everything seems to work fine, except when I push a 'merged_16bit' version.
For reference, I managed to push all the versions I wanted (Lora, GG…
-
I'm running a 16-bit application with otvm, however, there's an issue when the application try to invoke odbc.dll library that is compiled in 16-bit.
As otvdm converts instructions from 16 to 32 b…
-
The functions `M68kExpandPseudo::ExpandMI` and `M68kInstrInfo::ExpandMOVEM` unconditionally promote MOVEM instructions to their 32bit variant to allow collapsing multiple consecutive instructions. Thi…
-
### Feature request
A fused CUDA kernel that combine the dequantize main weight step and matrix multiplication, in order to reduce the data on-chip/off-chip movement.
### Motivation
I use profile t…
-
Hi, can the software work, and specially save, in 16bit depth png/tiff format?
If not, the height maps are useless, as 8bit images produce stepping artifacts.
-
Hi!
I'm not using Kaggle, but how can I get that exception?
I'm just trying to save gguf model.
model.save_pretrained_gguf("model", tokenizer, quantization_method = "f16")
RuntimeError: Unslot…
-
I am trying to get a 16bit output, floating point or 16bit int out of the app but it doesn't seem to obey the -FP16 flag.
I have tried sending through 16bit png, 16 bit int tif, and 32 floating point…
-
The assertion "Need DR8 register to copy CCR" in M68kInstrInfo::copyPhysReg appears to be wrong. According to the Programmer's Reference Manual, MOVE from CCR takes a 16bit destination operand and zer…
-
I have my project just using bpy to generate rendered images instead of opening blender. I need to generate depth image as 16bit to represent the depth information as milimeter but bpy seems only outp…