There are several things to report this month:
* The GCC version 5 branch has been created. No releases have been made from this branch yet, but when one happens it will be GCC 5.1. Meanwhile the mainline development sources have been switched to calling themselves GCC version 6.
* Support has been added for configuring targets that use the Nuxi CloudABI. More details of this ABI can be found here: https://github.com/NuxiNL/cloudlibc
* The linker and assembler now support an option to control how DWARF debug sections are compressed: --compress-debug-sections=[none|zlib|zli
Selecting none disables compression. This is the default behaviour if this option is not used. Selecting zlib or zlib-gnu compresses the sections and then renames them to start with a .z. This is the old method of indicating that a debug section has been compressed. Selecting zlib-gabi compresses the sections, but rather than renaming them they instead have the new SHF_COMPRESSED bit set in their ELF section header.
The other binutils tools have been updated to recognise and handle this SHF_COMPRESSED bit. More information on the new bit can be found here: https://groups.google.com/forum/#!msg/generic-abi/dBOS1H47Q64/PaJvELtaJrsJ
In another, related change, the binutils will no longer compress a debug section if doing so would actually make it bigger.
Also the zlib compression/decompression library sources have now been brought in to the binutils git repository and are now a standard part of a binutils release.
* The linker has a new command line option: --warn-orphan
This option tells the linker to generate a warning message whenever it has to guess at the placement of a section in the output file. This happens when the linker script in use does not specify where the section should go.
* The compiler has a new option: -fsanitize-sections=sec1,sec2,...
This tells the address sanitizer to add protection to global variables defined in the named section(s). By default any globals in sections with user defined names are not sanitized as the compiler does not know what is going to happen to them. In particular variables in such sections sometimes end up being merged into an array of values, where the presence of address sanitization markers would break the array.
* The AVR port of the compiler has a new command line option: -nodevicelib
This tells the compiler not to link against AVR-LibC's device specific library libdev.a.
* The RX port of GCC has a new command line option to disable the use of RX string instructions (SMOVF, SUNTIL, etc). This matters because it is unsafe to use these instructions if the program might access the I/O portion of the address space.
* The RL78 port of GCC now has support the multiply and divide instructions provided by the G14 cpu, and the divide hardware peripheral provided by the G13 core.
* GDB now honours the content of the file /proc/PID/coredump_filter on GNU/Linux systems. This file can be used to specify the types of memory mappings that will be include in a corefile. For more information, please refer to the manual page of "core(5)". GDB also has a new command: "set use-coredump-filter on|off". It allows to set whether GDB will read the content of the /proc/PID/coredump_filter file when generating a corefile.
* GDB's "info os cpus" command on GNU/Linux can now display information on the cpus/cores on the system.
* GDB has two new commands: "set serial parity odd|even|none" and "show serial parity". These allows to set or show parity for the remote serial I/O.