From: "Paulo Matos" <pmatos@broadcom.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Add IDENTIFIER_NODE to description of TARGET_ASM_NAMED_SECTION
Date: Fri, 19 Oct 2012 13:04:00 -0000 [thread overview]
Message-ID: <19EB96622A777C4AB91610E763265F46187CF4@SJEXCHMB14.corp.ad.broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
As a followup to:
http://gcc.gnu.org/ml/gcc/2012-10/msg00276.html
2012-10-19 Paulo Matos <pmatos@broadcom.com>
* tm.texi, tm.texi.in: Add IDENTIFIER_NODE as an alternative possibility
to possible values of decl.
Paulo Matos
[-- Attachment #2: doc.patch --]
[-- Type: application/octet-stream, Size: 1854 bytes --]
*** gcc/doc/tm.texi
--- gcc/doc/tm.texi 2012-10-19 13:35:08.811456000 +0100
*************** of the filename using this macro.
*** 7395,7401 ****
Output assembly directives to switch to section @var{name}. The section
should have attributes as specified by @var{flags}, which is a bit mask
of the @code{SECTION_*} flags defined in @file{output.h}. If @var{decl}
! is non-NULL, it is the @code{VAR_DECL} or @code{FUNCTION_DECL} with which
this section is associated.
@end deftypefn
--- 7395,7401 ----
Output assembly directives to switch to section @var{name}. The section
should have attributes as specified by @var{flags}, which is a bit mask
of the @code{SECTION_*} flags defined in @file{output.h}. If @var{decl}
! is non-NULL, it is the @code{IDENTIFIER_NODE}, @code{VAR_DECL} or @code{FUNCTION_DECL} with which
this section is associated.
@end deftypefn
*** gcc/doc/tm.texi.in
--- gcc/doc/tm.texi.in 2012-10-19 13:33:50.629602000 +0100
*************** of the filename using this macro.
*** 7283,7290 ****
Output assembly directives to switch to section @var{name}. The section
should have attributes as specified by @var{flags}, which is a bit mask
of the @code{SECTION_*} flags defined in @file{output.h}. If @var{decl}
! is non-NULL, it is the @code{VAR_DECL} or @code{FUNCTION_DECL} with which
! this section is associated.
@end deftypefn
@hook TARGET_ASM_FUNCTION_SECTION
--- 7283,7290 ----
Output assembly directives to switch to section @var{name}. The section
should have attributes as specified by @var{flags}, which is a bit mask
of the @code{SECTION_*} flags defined in @file{output.h}. If @var{decl}
! is non-NULL, it is the @code{IDENTIFIER_NODE}, @code{VAR_DECL} or
! @code{FUNCTION_DECL} with which this section is associated.
@end deftypefn
@hook TARGET_ASM_FUNCTION_SECTION
next reply other threads:[~2012-10-19 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 13:04 Paulo Matos [this message]
2012-10-19 14:07 ` Ian Lance Taylor
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=19EB96622A777C4AB91610E763265F46187CF4@SJEXCHMB14.corp.ad.broadcom.com \
--to=pmatos@broadcom.com \
--cc=gcc-patches@gcc.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).