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
For ex: when in uper mode, a value of 43980465111903 gives out -1 when compiled and linked in 32 bit mode (gcc -m32) or on an embedded box.
the problem is with the asn_per_constraints_t structure being treating the lower bound and upper bounds as 'long' data types than 64 bit generic data types in both machine architectures.
The text was updated successfully, but these errors were encountered:
lets consider a simple 42 bit number that is to be generated in the UPER format.
Timestamp ::= INTEGER (0..4398046511103)
When generated with the asn1c on the 32 bit X86 processor, it produces the Timestamp as a long variable. As the long variable is of length 4 bytes on the 32 bits architecture, the encoding always a failure when the integer value goes more than INT_MAX.
For ex: when in uper mode, a value of 43980465111903 gives out -1 when compiled and linked in 32 bit mode (gcc -m32) or on an embedded box.
the problem is with the asn_per_constraints_t structure being treating the lower bound and upper bounds as 'long' data types than 64 bit generic data types in both machine architectures.
The text was updated successfully, but these errors were encountered: