From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: PATCH: PR ld/12380: Assertion in linker script failed twice
Date: Mon, 10 Jan 2011 13:45:00 -0000 [thread overview]
Message-ID: <AANLkTi=WraO5Qz-rygZ1Td0E6qzmtgwtNsG-hVYq4qNX@mail.gmail.com> (raw)
In-Reply-To: <4D2B0C86.2030003@redhat.com>
On Mon, Jan 10, 2011 at 5:41 AM, Nick Clifton <nickc@redhat.com> wrote:
> Hi H.J.
>
>> This patch avoids duplicated assert messages. OK to install?
>
> The patch needs to include a testsuite entry as well.
>
I tried to create a testcase. But I couldn't find a way to check there was
no duplicated linker warning. The only testcase I can find is to check
the linker warning, which passes with and without my patch.
--
H.J.
next prev parent reply other threads:[~2011-01-10 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 18:05 H.J. Lu
2011-01-10 13:41 ` Nick Clifton
2011-01-10 13:45 ` H.J. Lu [this message]
2011-01-11 1:28 ` Alan Modra
2011-01-11 2:45 ` H.J. Lu
2011-01-11 5:38 ` Alan Modra
2011-01-11 5:51 ` H.J. Lu
2011-01-12 12:05 ` Alan Modra
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='AANLkTi=WraO5Qz-rygZ1Td0E6qzmtgwtNsG-hVYq4qNX@mail.gmail.com' \
--to=hjl.tools@gmail.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).