From: Viorel Preoteasa <viorel.preoteasa@gmail.com>
To: binutils@sourceware.org
Subject: Fix for bug 28924
Date: Wed, 9 Mar 2022 11:23:56 +0200 [thread overview]
Message-ID: <60ea0381-f92a-4c75-c07a-3f01baa1be90@gmail.com> (raw)
In-Reply-To: <20220309052506.4000271-3-amodra@gmail.com>
Hello,
We have a fix for bug 28924.
https://sourceware.org/bugzilla/show_bug.cgi?id=28924
The fix is very simple and involves very small changes (2 lines). How
can we have this fix applied? If I send the changes could someone apply
the fix?
I could also try to produce a test which does not depend on gcc that
reveals the problem. The dependency on gcc make the test unreliable.
Best regards,
Viorel Preoteasa
next prev parent reply other threads:[~2022-03-09 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 5:25 [PATCH 0/2] rh2059646 - compilation of prusa-slicer hangs Alan Modra
2022-03-09 5:25 ` [PATCH 1/2] Reduce duplicated symbol_clone_if_forward_ref work Alan Modra
2022-03-09 5:25 ` [PATCH 2/2] Constant fold view increment expressions Alan Modra
2022-03-09 9:23 ` Viorel Preoteasa [this message]
2022-03-09 11:42 ` Fix for bug 28924 Nick Clifton
2022-03-16 19:10 ` Viorel Preoteasa
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=60ea0381-f92a-4c75-c07a-3f01baa1be90@gmail.com \
--to=viorel.preoteasa@gmail.com \
--cc=binutils@sourceware.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).