Please help testing upcoming openMSX release! | MSX Resource Center (Página 1/68)

Champion (380)

25-09-2018, 14:24

That is quite an impressive list in the release notes!

I'm trying to build the latest master branch from github on Slackware 14.2 and I get this:

g++ \
	 -MP -MMD -MF derived/x86_64-linux-opt/dep/sound/DACSound16S.d \
	-o derived/x86_64-linux-opt/obj/sound/DACSound16S.o  -O3 -DNDEBUG -ffast-math -fomit-frame-pointer -pthread  -m64 -pipe -std=c++11 -Wall -Wextra -Wundef -Wno-invalid-offsetof -Wunused-macros -Wdouble-promotion -Wmissing-declarations -Wshadow -Wno-missing-field-initializers -std=c++14 -Isrc -Isrc/cassette -Isrc/commands -Isrc/config -Isrc/console -Isrc/cpu -Isrc/debugger -Isrc/events -Isrc/fdc -Isrc/file -Isrc/ide -Isrc/input -Isrc/laserdisc -Isrc/memory -Isrc/resource -Isrc/security -Isrc/serial -Isrc/settings -Isrc/sound -Isrc/thread -Isrc/unittest -Isrc/utils -Isrc/video -Isrc/video/ld -Isrc/video/scalers -Isrc/video/v9990 -Iderived/x86_64-linux-opt/config  -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/freetype2   -I/usr/include -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT     -I/usr/include/libpng16  -c src/sound/DACSound16S.cc
src/sound/BlipBuffer.cc:96:51:   in constexpr expansion of ‘openmsx::calcImpulses()’
src/sound/BlipBuffer.cc:96:51: error: modification of ‘*((& fimpulse[1024]) + 8u)’ is not a constant-expression
 static CONSTEXPR Impulses impulses = calcImpulses();

This is probably due to gcc version 5.5.0 I guess?

Por wouter_

Hero (535)

25-09-2018, 20:50

Philip wrote:

... This is probably due to gcc version 5.5.0 I guess?

Thanks for testing!
I've investigated and you're right: it's due to a limitation/bug in gcc-5.x (gcc-6 and above work fine).
I've added a workaround: gcc-5.x now falls back to the old code (calculate some lookup tables at run-time rather than compile-time). Please update to the latest git revision and try again.

Por Manuel

Ascended (19677)

25-09-2018, 21:23

It also worked fine on gcc-4.9, so I guess it's quite a specific bug of 5.5.

Por Philip

Champion (380)

26-09-2018, 15:45

Just tried the latest git revision and it works fine now. Thanks for fixing it so quickly.
I also tried the latest git revision of catapult and the debugger and these also work great.

So that means I can update the Slackware packages once the new version is released B-)

Por Manuel

Ascended (19677)

26-09-2018, 16:11

Yeah, but next version we will remove this workaround, so let's hope Slackware has a modern g++ then

Por Philip

Champion (380)

26-09-2018, 16:56

It probably will if you don't release the next version to quickly

Por eimaster

Champion (285)

27-09-2018, 06:02

openMSX for Android on screen button 1, 2, and arrows are not working in Games! I just can play with Android Haker keyboard which is not practical because the keyboard eats up half of the game screenplay beside it is a bit slow. I don't know what happened! I used to play normally before (using the previous build, but since I installed the new build I cannot play or make things move with on-screen arrows and buttons 1 and 2!
Can anybody help identify the problem so it can be fixed?!

Por Manuel

Ascended (19677)

27-09-2018, 07:26

Strange, it works just fine here. Can someone confirm?

Por santiontanon

Paragon (1831)

30-09-2018, 05:42

I've tried a few games and a few different machines on a Mac OS 10.12 machine, and all ran smooth!!

Por Manuel

Ascended (19677)

30-09-2018, 08:56

eimaster wrote:

openMSX for Android on screen button 1, 2, and arrows are not working in Games! I just can play with Android Haker keyboard which is not practical because the keyboard eats up half of the game screenplay beside it is a bit slow. I don't know what happened! I used to play normally before (using the previous build, but since I installed the new build I cannot play or make things move with on-screen arrows and buttons 1 and 2!
Can anybody help identify the problem so it can be fixed?!

Can you find out exactly which was the latest version that worked and which was the first version that did not work? That may give some hints on what is going on.
Also, I hope other people can also check whether it works for them. E.g. for Paulo it works fine (except in Guru Logic): https://www.msx.org/forum/msx-talk/openmsx/touchscreen-butto...
Which game did you try, eimaster?