From: Nick Clifton <nickc@redhat.com>
To: Thomas Schwinge <tschwinge@gnu.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: PATCH: PR ld/12730: regression] crash when allocating in a static constructor
Date: Tue, 21 Jun 2011 15:14:00 -0000 [thread overview]
Message-ID: <4E00B578.90908@redhat.com> (raw)
In-Reply-To: <87oc1tzl3w.fsf@kepler.schwinge.homeip.net>
Hi Thomas,
> Why, oh why? :-)
:)
> ld/testsuite/
>
> * ld-elf/elf.exp: Execute array_tests_pie tests on *-*-gnu*, too.
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2011-06-21 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 5:19 H.J. Lu
2011-05-05 8:27 ` Alan Modra
2011-05-05 13:27 ` H.J. Lu
2011-05-05 14:13 ` Alan Modra
2011-05-06 13:23 ` H.J. Lu
2011-05-06 16:16 ` H.J. Lu
2011-05-07 8:11 ` Alan Modra
2011-05-07 13:40 ` H.J. Lu
2011-05-07 14:05 ` Alan Modra
2011-05-09 13:53 ` Alan Modra
2011-05-09 14:09 ` H.J. Lu
2011-06-19 19:18 ` Thomas Schwinge
2011-06-21 15:14 ` Nick Clifton [this message]
2011-05-15 10:14 Craig Southeren
2011-05-16 0:15 ` Alan Modra
2011-05-16 0:37 ` Craig Southeren
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=4E00B578.90908@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=tschwinge@gnu.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).