From: Viorel Preoteasa <viorel.preoteasa@gmail.com>
To: Nick Clifton <nickc@redhat.com>, Alan Matsuoka <alanm@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: Fix for bug 28924
Date: Wed, 16 Mar 2022 21:10:06 +0200 [thread overview]
Message-ID: <62f7132a-9300-dbc4-0fc9-db3cd2fa2bf7@gmail.com> (raw)
In-Reply-To: <11f7dfc6-a4b4-6b4c-ea1e-a100f398d5b1@redhat.com>
Hi Nick,
I noticed that you answered the bug 28924. I have now added a file that
can be used to reproduce the problem, and I added also the information
required to fix the problem.
Viorel
On 3/9/2022 1:42 PM, Nick Clifton wrote:
> Hi Viorel,
>
>> 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?
>
> Please submit the patch to the binutils mailing list, so that it can
> be reviewed.
>
> It would also help if you can add a link to the email to PR 28924,
> once the email
> appears in the binutils mailing list archive.
>
>
>> 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.
>
> That would be appreciated. A patch that includes a test is always
> better than
> one that does not.
>
> Cheers
> Nick
>
prev parent reply other threads:[~2022-03-16 19:10 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 ` Fix for bug 28924 Viorel Preoteasa
2022-03-09 11:42 ` Nick Clifton
2022-03-16 19:10 ` Viorel Preoteasa [this message]
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=62f7132a-9300-dbc4-0fc9-db3cd2fa2bf7@gmail.com \
--to=viorel.preoteasa@gmail.com \
--cc=alanm@redhat.com \
--cc=binutils@sourceware.org \
--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).