From: Patrick Oppenlander <patrick.oppenlander@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] armv7-m musl 1.2.0 toolchain crash
Date: Tue, 17 Mar 2020 11:40:49 +1100 [thread overview]
Message-ID: <CAEg67GkMJGrFz8pDPh222CoiqVTi6RoXqi8VO0OHgJRpkib9nA@mail.gmail.com> (raw)
In-Reply-To: <20200316175428.GV11469@brightrain.aerifal.cx>
On Tue, Mar 17, 2020 at 4:54 AM Rich Felker <dalias@libc.org> wrote:
>
> Can you clarify if the change is that the toolchain is built against
> musl 1.2.0 and now malfunctioning, or trying to link to musl 1.2.0 and
> now malfunctioning? Those are very different and it's not clear which.
>
Sorry, my previous email was no where near clear enough. I'll try to
do better this time :)
All of my toolchains are built against glibc as I build them with the
default host compiler on my Arch Linux system.
I typed out a huge email detailing dozens of tests which I performed,
but it's all irrelevant and boils down to the following:
gcc / binutils / musl / C++ link
7.4.0 / 2.27 / 1.2.0 / works
7.4.0 / 2.32 / 1.2.0 / fails
7.4.0 / 2.33.1 / 1.2.0 / fails
7.4.0 / 2.34 / 1.2.0 / works (binutils-2.34 no mcm patches)
9.2.0 / 2.34 / 1.2.0 / works
9.3.0 / 2.34 / 1.2.0 / works (using mcm gcc 9.2.0 patches)
So it looks to me like there was a regression in binutils introduced
after version 2.27 and fixed in 2.34.
BTW, the gcc 9.2.0 patches apply with some fuzz to 9.3.0 with the
exception of 0017-pr93402.diff which is upstream. I'll do further
testing over the next week or two on the gcc 9.3.0 arm & armv7m
targets with binutils 2.34 and musl 1.2.0.
Hope that helps,
Patrick
next prev parent reply other threads:[~2020-03-17 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 5:41 Patrick Oppenlander
2020-03-16 17:54 ` Rich Felker
2020-03-17 0:40 ` Patrick Oppenlander [this message]
2020-03-18 19:10 ` Szabolcs Nagy
2020-03-18 22:43 ` Patrick Oppenlander
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=CAEg67GkMJGrFz8pDPh222CoiqVTi6RoXqi8VO0OHgJRpkib9nA@mail.gmail.com \
--to=patrick.oppenlander@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).