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
While testing #704, jnthn ended up with long long as INTVAL type and long as opcode_t type. This, however, is not a working combination - the build failed at
.\miniparrot.exe -Iruntime/parrot/include -o frontend/parrot2/prt0.pbc frontend/parrot2/prt0.pir
PackFile_pack segment 'DIRECTORY' used size 2368 but reported 2664
This issue probably never turned up before as the configuration step inter::types discards the configuration option --opcode and changes it to either --intval if present or long.
The only way one could end up with different values before my refactor of auto::sizes was manually skipping configuration steps or entering interactive mode via --ask, which obviously is not something normally done.
It should be discussed whether differing types should be supported at all. If so, the codebase needs to be fixed. If not, the --opcode configuration option should be removed.
The text was updated successfully, but these errors were encountered:
While testing #704, jnthn ended up with
long longasINTVALtype andlongasopcode_ttype. This, however, is not a working combination - the build failed atThis issue probably never turned up before as the configuration step
inter::typesdiscards the configuration option--opcodeand changes it to either--intvalif present orlong.The only way one could end up with different values before my refactor of
auto::sizeswas manually skipping configuration steps or entering interactive mode via--ask, which obviously is not something normally done.It should be discussed whether differing types should be supported at all. If so, the codebase needs to be fixed. If not, the
--opcodeconfiguration option should be removed.The text was updated successfully, but these errors were encountered: