summaryrefslogtreecommitdiffstatshomepage
path: root/3rdparty/softfloat3
Commit message (Collapse)AuthorAgeFilesLines
* 3rdparty: Retired softfloat2. (#15270) Patrick Mackinlay2026-04-282-0/+74
| | | cpu/i386, machine/i8087.cpp: Migrated to SoftFloat 3.
* 3rdparty/softfloat3: Proper way to detect presence of __int128 on GCC/clang. Vas Crabb2025-04-201-5/+6
|
* m68k: add FPU instructions `FETOX`, `FETOXM1`, `FTWOTOX`, `FTENTOX` (#12903) kms12122024-10-242-19/+327
|
* cpu/m68000: FPU now sets the NaN flag for all NaNs, not just signalling. ↵ arbee2024-05-302-0/+6
| | | | Fixes dendego black screen in attract mode. [R. Belmont]
* cpu/m68000: Updated 680x0 FPU to Softfloat 3 from 2. (MT5411 and MT8793). ↵ arbee2024-05-2715-22/+2468
| | | | | | | | | | | | | | | | | | [R. Belmont] - Update to Softloat 3 from 2 - FREM and FMOD now generate the quotient bits in FPSR, required by Apple's SANE to do sin/cos/tan properly. - FMOVE of a float to a Dx integer register generates the exception status bits, fixing square roots in SANE - Rewrote how FMOVEM instructions are decoded and executed, fixing issues including skipping too few or too many opcode bytes and causing serious weird behavior. - FPU instructions all now have more realistic cycle timings for a 68881. - All FPU instructions now generate exception bits in FPSR. 3rdparty/softfloat3: Updates [R. Belmont] - Softfloat3 was always being built for a big-endian host, causing incorrect math on LE x64 and AArch64 machines. - Fixed up Softfloat3 to build properly as part of MAME and up-ported the Bochs extensions. In latest Bochs, they were only partially up-ported and Softfloat3 had been hacked up to be more like 2; here they're fixed to work with stock Softfloat3.
* (nw) Clean up the mess on master Vas Crabb2019-03-261-1/+1
| | | | | | | | | | | | | This effectively reverts b380514764cf857469bae61c11143a19f79a74c5 and c24473ddff715ecec2e258a6eb38960cf8c8e98e, restoring the state at 598cd5227223c3b04ca31f0dbc1981256d9ea3ff. Before pushing, please check that what you're about to push is sane. Check your local commit log and ensure there isn't anything out-of-place before pushing to mainline. When things like this happen, it wastes everyone's time. I really don't need this in a week when real work™ is busting my balls and I'm behind where I want to be with preparing for MAME release.
* Revert "conflict resolution (nw)" andreasnaive2019-03-251-1/+1
| | | | | This reverts commit c24473ddff715ecec2e258a6eb38960cf8c8e98e, reversing changes made to 009cba4fb8102102168ef32870892438327f3705.
* silence MS-LLVM (nw) Peter Ferrie2019-02-161-1/+1
|
* Fix softfloat3 build with MSVC 32-bit. Apparenly it's all-or-nothing with ↵ Vas Crabb2018-05-271-7/+14
| | | | built-in leading zero count. (nw)
* softfloat3: fix msvc build (nw) (#3566) Patrick Mackinlay2018-05-141-1/+10
| | | | | | | | | | | | * softfloat3: fix msvc build (nw) Is this how we do these things? I assume we don't touch the library code itself, and have to "fix" any problems via this header instead? * softfloat3: do we like this better? (nw) * softfloat3: it gets the hose again (nw) * softfloat3: sonofa (nw)
* Initial import of SoftFloat release 3E [R. Belmont] arbee2018-05-13452-0/+47220
This is a pre-usage import so everyone can get things in line for various compilers. GCC/Clang should be OK on most targets as-is; MSVC may need to edit 3rdparty/softfloat3/build/MAME/build.h to conform. Please report failure/success with various compilers.