F29 System Wide Change: Binutils 2.31
= Proposed System Wide Change: Binutils 2.31 =
https://fedoraproject.org/wiki/Changes/BINUTILS231
Owner(s):
* Nick Clifton <nickc at redhat dot com>
Rebase the binutils package from version 2.30 to version 2.31.
== Detailed description ==
Switch the binutils package from being based on the 2.30 release of
the FSF binutils to being based on the 2.31 release. This release
will bring in numerous bug fixes, as well as the following new
features:
The linker can now put all code and read-only data sections into a
separate segment with only READ and EXECUTE permissions. All writable
data can be placed into a separate segment with READ and WRITE
permissions. This makes programs larger, but safer. The linker's
behaviour can be controlled via a command line option, and the default
set by a configure option.
The assembler can generate build notes for any input files which do
not contain their own notes. Again this is controlled via a command
line option whose default is set by a configure option.
The x86 assembler supports a new -O[2|s] command-line option to enable
alternate, shorter instruction encoding. It also supports a ,nop
pseudo-op to simplify the insertion of NOP instruction sequences.
The AArch64 assembler will now warn a combintation of an instruction
and a register name are invalid. The AArch64 disassembler will now
also flag inconsistent instruction encodings.
The "ar" program will now accept an "O" modifier to its command line,
which causes the offsets of members within the archive to be displayed
alongside the other information.
== Scope ==
* Proposal owners:
Change the source parameter in the binutils.spec rpm and adjust the
local patches to take account of the bugs that are now already
fixed.This should be followed by a mass rebuild in order for the
changes to be noticed across the system.
* Other developers:
No other work should be necessary. Once the rebase is in place and
the buildroot contains the new binutils its use should be automatic.It
is possible that the new linker feature might prove to be problematic
forsome packages, although no such problems are anticipated. If this
doeshappen however the package maintainers can add a command line
optionto disable the new linker feature.
* Release engineering:
https://pagure.io/releng/issue/7573
** List of deliverables:
Just the binutils package.
* Policies and guidelines:
No updates needed.
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
JBoss EAP Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic