From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2012.12.1 released
Date: Fri, 15 Feb 2013 12:57:53 +0100 [thread overview]
Message-ID: <20130215115753.GB24375@pengutronix.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1431 bytes --]
Hi,
I've uploaded the tarball for the latest OSELAS.Toolchain stable release.
It's v2012.12.1 and can be downloaded here:
http://www.pengutronix.de/oselas/toolchain/download/
This is a bugfix only release. The relevant changes are:
- arm-1136jfs-linux-gnueabihf now reports the correct LDSO which makes this
toolchain actually usable.
- i686-atom-linux-gnu does not use 'movbe' by default any more. This way
the produced code should run on CPUs >= Core2 as well.
- Bugfixes for gcc bugs 55981 and 56028. This is about 64-bit atomics that
are not actually atomic. This is an x86 issue only.
Enjoy,
Michael
The complete shortlog:
Michael Olbrich (7):
gcc-4.7.2: add patch to fix specs for arm-1136jfs-linux-gnueabihf
ptxconfig: i686-atom-linux-gnu: don't use movbe by default
ptxconfig: i686-atom-linux-gnu: fix typo in the last commit
gcc: add patch for: Bug 55981 - std::atomic store is split in two smaller stores
gcc: remove changelog entries from patch
gcc: add patch for: Bug 56028 - Splitting a 64-bit volatile store
release 2012.12.1
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2013-02-15 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 11:57 Michael Olbrich [this message]
2013-02-16 11:36 ` Bernhard Walle
2013-02-20 18:00 ` Michael Olbrich
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=20130215115753.GB24375@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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