From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org, info-gnu@gnu.org, dje.gcc@gmail.com
Subject: GNU Binutils 2.34 released
Date: Sat, 01 Feb 2020 12:56:00 -0000 [thread overview]
Message-ID: <87y2tmo491.fsf@redhat.com> (raw)
Hi Everyone,
We are pleased to announce that version 2.34 of the GNU Binutils project
sources have been released and are now available for download at:
https://ftp.gnu.org/gnu/binutils
https://sourceware.org/pub/binutils/releases/
The md5 checksums are:
b0afc4d29db31ee6fdf3ebc34e85e482 binutils-2.34.tar.bz2
079f3414a4c2b8f58e05acfd03b57355 binutils-2.34.tar.gz
eda15400c0e76f4a152ef2505e7204d2 binutils-2.34.tar.lz
664ec3a2df7805ed3464639aaae332d6 binutils-2.34.tar.xz
This release contains numerous bug fixes, and also the
following new features:
* The disassembler (objdump --disassemble) now has an option to
generate ascii art thats show the arcs between that start and end
points of control flow instructions.
* The binutils tools now have support for debuginfod. Debuginfod is a
HTTP service for distributing ELF/DWARF debugging information as
well as source code. The tools can now connect to debuginfod
servers in order to download debug information about the files that
they are processing.
* The assembler and linker now support the generation of ELF format
files for the Z80 architecture.
Our thanks go out to all of the binutils contributors, past and
present, for helping to make this release possible.
Cheers
Nick Clifton
next reply other threads:[~2020-02-01 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 12:56 Nick Clifton [this message]
2020-02-06 15:59 ` H.J. Lu
2020-02-07 11:00 ` Nick Clifton
2020-02-07 11:18 ` Jozef Lawrynowicz
2020-02-07 12:06 ` H.J. Lu
2020-02-07 15:12 ` Nick Clifton
2020-02-07 15:35 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2tmo491.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=dje.gcc@gmail.com \
--cc=info-gnu@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).