EmuCR Feeds
Email Us

EmuCR:OpenMSX OpenMSX Git (2016/06/18) is complie. OpenMSX is an open source MSX emulator which is free according to the Debian Free Software Guidelines, available under the GNU General Public License.For copyright reasons the emulator cannot be distributed with original BIOS ROM images. OpenMSX includes C-BIOS a minimal implementation of the MSX BIOS, allowing to play quite some games without the need to have an original MSX BIOS ROM image. You can also use your own BIOS ROM image if you please.

OpenMSX Git Changelog:
* Fix(?) visual studio compiler error
Use 'ptrdiff_t' instead of 'ssize_t'.
* Removed some unreachable code
Found by clang-tidy [clang-analyzer-alpha.deadcode.UnreachableCode].
* Removed redundant unique_ptr::get() call
This fixes all warnings given by clang-tidy [misc-redundant-smartptr-get].
* Replaced some '(unsigned) long' types with '(s)size_t'
The intention of this code was to use a type with the same size as a pointer.
Not for correctness but because gcc generated slightly better code for it (less
zero-extension instructions). Using the type 'long' for this works perfectly on
Linux (it's 32/64 bits on respectively 32/64-bit systems). But on windows
'long' is always 32-bit (also on 64-bit systems). However 'size_t' does work.
Suggested by clang-tidy [google-runtime-int].
* Mark single-parameter constructors 'implicit'
This prevents accidental implicit conversions. Changes suggested by clang-tidy
[google-explicit-constructor].
In a few cases (e.g. string_ref and array_ref) we do want these implicit
conversions. I marked those constructors with /*implicit*/.
* Replace 'short' with 'int16_t'
More clearly expresses the intend (and might also make the code more portable).
Suggested by clang-tidy [google-runtime-int].
In a few places where the type really didn't matter I replaced 'short' with
'int'.
* Fix debug build with gcc-6

Download: OpenMSX Git (2016/06/18) x86
Download: OpenMSX Git (2016/06/18) x64
Source: Here

Random Related Topic Refresh Related Topic

Random Related Topic Loading...

0 Comments

Post a Comment

Can't post a comment? Try This!