Closed LigH-de closed 5 years ago
Still no reaction. May it be appropriate to raise the priority in the VVC tracker after 2 weeks?
Or maybe it should be restricted to 64-bit only. If upstream doesn't give a shit about 32-bit, there's really no point trying to support it.
Edit: ^
Perhaps, but at the same time, most likely 32-bit probably is not even close to a high enough priority for them since they are only encoding plus a lot of distros are dropping 32-bit, although not necessarily 32-bit libs.
@LigH-de, do you feel that vvc is important enough to keep on with 32-bit compilation? We can disable temporarily until they at least respond.
You don't need to restrict it to 64-bit only compilation as the suite treats this project as optional, already. It continues after failing to compile in 32-bit mode. But getting practically restricted by the developers in the future would not surprise me: VVC is slow as hell. Trying to execute it on 32-bit only hardware can't be recommendable. And already x265 required more RAM than 32-bit addresses could provide, to encode HD resolutions.
I hope changing the priority boldly may provoke them to any reaction.
It was probably a good choice to disable 32-bit building. I see a drop for support coming, rather than "fixing" it:
Thanks for the report. VTM does not work properly in 32-bit due to big amount of memory used. Although We have an MR on memory reduction, it may not solve all the issues with 32-bit. It is suggested to test with 64-bit compiler. Fix and improvement for 32-bit are appreciated.
I will close this report now. If I ever get a notice about a patch to re-enable 32-bit compilation, I may tell about it here...
VVC staff officially stated that x86 (32-bit) is no target for VVC, at least not the reference software. Custom projects may or may not support it.
Reported to Fraunhofer trac VVC ticket #620. Not blocking MABS as it treats this project as optional.