From: Cary Coutant <ccoutant@google.com>
To: Ian Lance Taylor <iant@google.com>
Cc: John Marino <binutils@marino.st>, binutils@sourceware.org
Subject: Re: suggestion for gold's testsuite makefile (initpri2 LDFLAGS)
Date: Thu, 16 Feb 2012 19:39:00 -0000 [thread overview]
Message-ID: <CAHACq4pxNC0nJB4uP6NgBo0os5QOgHvvtZNuvb2V2EgKcAx=Xw@mail.gmail.com> (raw)
In-Reply-To: <mcrehtv5xsm.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
>> I don't think anybody responded to this post from last week, but I
>> don't want it to fall between the cracks. Is it a good idea to modify
>> the gold testsuite makefile with this change?
>
> Yes, it's fine. The obvious patch is preapproved if anybody cares to
> commit it.
I have committed this change:
* testsuite/Makefile.am (initpri2): Add --ctors-in-init-array option.
* testsuite/Makefile.in: Regenerate.
-cary
prev parent reply other threads:[~2012-02-16 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 12:07 John Marino
2012-02-15 9:28 ` John Marino
2012-02-16 2:15 ` Ian Lance Taylor
2012-02-16 19:39 ` Cary Coutant [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='CAHACq4pxNC0nJB4uP6NgBo0os5QOgHvvtZNuvb2V2EgKcAx=Xw@mail.gmail.com' \
--to=ccoutant@google.com \
--cc=binutils@marino.st \
--cc=binutils@sourceware.org \
--cc=iant@google.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).