You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This almost falls into Issue #3, but it's a bit worse than just having a bunch of x86 asm everywhere. There is a lot of pointer-y stuff being thrown about, and on 64-bit this gets ugly fast due to everything being written with only 32-bit in mind.
It's hard to determine if the errors will be genuinely problematic or if it's just bad precision at the compilation stage. Just fix them as you see them, but get worried if the errors hover around areas that directly deal with MadTracker-related data. That will probably mean redesigning the file format to work on any architecture.
The text was updated successfully, but these errors were encountered:
[ 1%] Building CXX object CMakeFiles/madtracker3.dir/MT3/MTExtensions.cpp.o
/home/ammon/NetBeansProjects/MadTracker3/MT3/MTExtensions.cpp: In member function ‘virtual void MT3Interface::notify(void_, int, int)’:
/home/ammon/NetBeansProjects/MadTracker3/MT3/MTExtensions.cpp:309:38: error: cast from ‘void_’ to ‘int’ loses precision [-fpermissive]
/home/ammon/NetBeansProjects/MadTracker3/MT3/MTExtensions.cpp: In member function ‘virtual bool MT3Interface::editobject(void_, bool)’:
/home/ammon/NetBeansProjects/MadTracker3/MT3/MTExtensions.cpp:385:22: error: cast from ‘void_’ to ‘int’ loses precision [-fpermissive]
/home/ammon/NetBeansProjects/MadTracker3/MT3/MTExtensions.cpp: In function ‘void unloadExtensions()’:
/home/ammon/NetBeansProjects/MadTracker3/MT3/MTExtensions.cpp:777:10: warning: deleting object of polymorphic class type ‘MT3Interface’ which has non-virtual destructor might cause undefined behaviour [-Wdelete-non-virtual-dtor]
make[2]: *** [CMakeFiles/madtracker3.dir/MT3/MTExtensions.cpp.o] Error 1
make[1]: *** [CMakeFiles/madtracker3.dir/all] Error 2
make: *** [all] Error 2
This almost falls into Issue #3, but it's a bit worse than just having a bunch of x86 asm everywhere. There is a lot of pointer-y stuff being thrown about, and on 64-bit this gets ugly fast due to everything being written with only 32-bit in mind.
It's hard to determine if the errors will be genuinely problematic or if it's just bad precision at the compilation stage. Just fix them as you see them, but get worried if the errors hover around areas that directly deal with MadTracker-related data. That will probably mean redesigning the file format to work on any architecture.
The text was updated successfully, but these errors were encountered: