[Bug binutils/10368] ISO 8859 mentioned as 7bit encoding in strings documentation

https://sourceware.org/bugzilla/show_bug.cgi?id=10368 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b8d7a9572d7e934be23f3b7ef74880e56957c233 commit b8d7a9572d7e934be23f3b7ef7488

[Bug binutils/10368] ISO 8859 mentioned as 7bit encoding in strings documentation

https://sourceware.org/bugzilla/show_bug.cgi?id=10368 Alan Modra changed: What|Removed |Added Status|NEW |RESOLVED Assignee|unassigned a

[Bug binutils/25202] objcopy --verilog-data-width doesn't respect target's endianness

https://sourceware.org/bugzilla/show_bug.cgi?id=25202 --- Comment #20 from Nick Clifton --- (In reply to Gökçe Aydos from comment #19) Hi Gökçe, > 1) Output is wrong if data-width>16. Does the verilog memory file format actually support widths greater than 16 ? (I have never used it, so maybe

[Bug binutils/25202] objcopy --verilog-data-width doesn't respect target's endianness

https://sourceware.org/bugzilla/show_bug.cgi?id=25202 --- Comment #21 from Olof Kindgren --- Thanks for keeping working on this. I'm afraid I haven't had any time to test it myself but it looks like we're on the right track. Yes, the data can be as wide as it needs to be. There's probably some up

[Bug ld/10933] libbfd and libopcodes don't support multilib

https://sourceware.org/bugzilla/show_bug.cgi?id=10933 H.J. Lu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---