Hi, Thanks for the clarification. You're right that the loader already reserves enough space for the setup header, so I will narrow the report wording to focus on the header-derived length and its signedness/unsigned interpretation rather than on destination space reservation. Best regards, Pengpeng