https://sourceware.org/bugzilla/show_bug.cgi?id=30444
--- Comment #15 from Sven <sven.koehler at gmail dot com> --- (In reply to Sven from comment #2) > //AAph7S is an example of a section name from the attached file. The part > after the two slashed decodes to the byte sequence 00 0a 61 ed. So i'm > pretty sure, the byte order is big endian. Given the new results, I should mention that I was wrong an //AAph7S decodes to 0xa61ed2. In test-llvm.o, there are also //base64 examples that end in a slash, which would not happen when encoding 32bit with RFC base64. For example //AAoQj/ decodes to 0xa108ff. -- You are receiving this mail because: You are on the CC list for the bug.
