From: Alan Modra <amodra@gmail.com>
To: Catherine Moore <clm@codesourcery.com>
Cc: binutils@sourceware.org
Subject: Re: PING Re: [RFA] Linker script extension SECTION_FLAGS
Date: Thu, 09 Feb 2012 05:27:00 -0000 [thread overview]
Message-ID: <20120209052642.GQ22267@bubble.grove.modra.org> (raw)
In-Reply-To: <4E0CE648.2080105@codesourcery.com>
On Thu, Jun 30, 2011 at 05:10:32PM -0400, Catherine Moore wrote:
[snip]
> (input_section_spec_no_keep): Add alternatives to recognize
> sect_flags.
[snip]
A compiler warning about 'tmp' set but not used prompted this patch.
Applied mainline.
* ldgram.y (input_section_spec_no_keep): Don't ignore sect_flags.
Index: ld/ldgram.y
===================================================================
RCS file: /cvs/src/src/ld/ldgram.y,v
retrieving revision 1.66
diff -u -p -r1.66 ldgram.y
--- ld/ldgram.y 11 Jul 2011 15:03:09 -0000 1.66
+++ ld/ldgram.y 9 Feb 2012 05:09:14 -0000
@@ -629,7 +629,7 @@ input_section_spec_no_keep:
tmp.exclude_name_list = NULL;
tmp.sorted = none;
tmp.section_flag_list = $1;
- lang_add_wild (NULL, $3, ldgram_had_keep);
+ lang_add_wild (&tmp, $3, ldgram_had_keep);
}
| wildcard_spec '(' file_NAME_list ')'
{
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2012-02-09 5:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 19:32 Catherine Moore
2011-05-18 19:33 ` Catherine Moore
2011-05-19 0:07 ` Ian Lance Taylor
2011-05-24 22:57 ` Catherine Moore
2011-05-25 12:28 ` Tristan Gingold
2011-06-06 22:02 ` PING " Catherine Moore
2011-06-07 13:11 ` Nick Clifton
2011-06-22 21:32 ` Catherine Moore
2011-06-28 11:37 ` Nick Clifton
2011-06-28 11:56 ` Tristan Gingold
2011-06-28 12:22 ` Nick Clifton
2011-06-28 13:30 ` Ian Lance Taylor
2011-06-30 21:11 ` Catherine Moore
2011-07-11 13:55 ` Nick Clifton
2012-02-09 5:27 ` Alan Modra [this message]
2011-05-19 7:44 ` Tristan Gingold
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=20120209052642.GQ22267@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=clm@codesourcery.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).