From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Cc: Nick Alcock <nick.alcock@oracle.com>,
Nick Clifton <nickc@redhat.com>,
Matthias Klose <matthias.klose@canonical.com>
Subject: Re: The 2.40 branch has been created
Date: Tue, 10 Jan 2023 12:43:32 +0000 [thread overview]
Message-ID: <87r0w2r24r.fsf@esperi.org.uk> (raw)
In-Reply-To: <87wn62sdel.fsf@esperi.org.uk> (Nick Alcock via Binutils's message of "Wed, 04 Jan 2023 12:16:34 +0000")
On 4 Jan 2023, Nick Alcock via Binutils stated:
> On 2 Jan 2023, Matthias Klose via Binutils stated:
>> On 31.12.22 14:00, Nick Clifton via Binutils wrote:
>> i686-linux-gnu:
>>
>> Running /<<PKGBUILDDIR>>/ld/testsuite/ld-ctf/ctf.exp ...
>> FAIL: Diagnostics - No parent dictionary
>
> This seems to be a cross-platform issue, which is strange because I've
> never seen this test (ld/testsuite/ld-ctf/diag-parname.d) fail: for me,
> it doesn't fail now, even with current 2.40 branch. This stuff is not
> compiler-dependent, so I'd expect to see identical failures for
> everybody.
I have a fix for this one under test (see the last patch in the series I
just sent). It's a type confusion that involves treating one struct as
if it were a much bigger one (and then writing to it, ugh), so it comes
down to accessing uninitialized memory. Hence the irreproducibility.
I'll backport the fix to all affected branches (2.36+).
This is now bug 29983.
next prev parent reply other threads:[~2023-01-10 12:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 13:00 Nick Clifton
2023-01-02 11:41 ` Matthias Klose
2023-01-02 11:56 ` Matthias Klose
2023-01-02 12:03 ` Andreas Schwab
2023-01-02 15:59 ` Christophe Lyon
2023-01-02 23:05 ` Mark Wielaard
2023-01-03 17:29 ` Christophe Lyon
2023-01-04 0:35 ` Mark Wielaard
2023-01-04 10:31 ` Christophe Lyon
2023-01-04 11:07 ` Mark Wielaard
2023-01-09 16:00 ` Christophe Lyon
2023-01-04 12:16 ` Nick Alcock
2023-01-10 12:43 ` Nick Alcock [this message]
2023-01-04 3:05 ` Alan Modra
2023-01-04 9:36 ` Nick Clifton
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=87r0w2r24r.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=matthias.klose@canonical.com \
--cc=nickc@redhat.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.
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).