public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: dorit@il.ibm.com, fjahanian@apple.com, bonzini@gnu.org,
	echristo@redhat.com, kkojima@gcc.gnu.org, roger@eyesopen.com,
	zack@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: New and undocumented target hooks (cf. PR3386, a regression)
Date: Fri, 03 Dec 2004 23:16:00 -0000	[thread overview]
Message-ID: <20041203231514.GC22293@redhat.com> (raw)
In-Reply-To: <6972371.1102079776822.SLOX.WebMail.wwwrun@extimap.suse.de>

On Fri, Dec 03, 2004 at 02:16:16PM +0100, Steven Bosscher wrote:
> 2002-12-09  Richard Henderson  <rth@redhat.com>
> TARGET_CANNOT_FORCE_CONST_MEM
> 2003-10-29  Richard Henderson  <rth@redhat.com>
> TARGET_BUILD_BUILTIN_VA_LIST

Done.


r~



Index: tm.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.400
diff -c -p -d -r1.400 tm.texi
*** tm.texi	3 Dec 2004 15:37:14 -0000	1.400
--- tm.texi	3 Dec 2004 23:13:38 -0000
*************** The default value of this hook is @code{
*** 3925,3930 ****
--- 3925,3935 ----
  false.
  @end deftypefn
  
+ @deftypefn {Target Hook} tree TARGET_BUILD_BUILTIN_VA_LIST (void)
+ This hook returns a type node for @code{va_list} for the target.
+ The default version of the hook returns @code{void*}.
+ @end deftypefn
+ 
  @deftypefn {Target Hook} tree TARGET_GIMPLIFY_VA_ARG_EXPR (tree @var{valist}, tree @var{type}, tree *@var{pre_p}, tree *@var{post_p})
  This hook performs target-specific gimplification of
  @code{VA_ARG_EXPR}.  The first two parameters correspond to the
*************** an immediate operand on the target machi
*** 5151,5156 ****
--- 5156,5173 ----
  anything @code{CONSTANT_P} is valid.
  @end defmac
  
+ @deftypefn {Target Hook} bool TARGET_CANNOT_FORCE_CONST_MEM (rtx @var{x})
+ This hook should return true if @var{x} is of a form that cannot (or
+ should not) be spilled to the constant pool.  The default version of
+ this hook returns false.
+ 
+ The primary reason to define this hook is to prevent reload from
+ deciding that a non-legitimate constant would be better reloaded
+ from the constant pool instead of spilling and reloading a register
+ holding the constant.  This restriction is often true of addresses
+ of TLS symbols for various targets.
+ @end deftypefn
+ 
  @node Condition Code
  @section Condition Code Status
  @cindex condition code status

  parent reply	other threads:[~2004-12-03 23:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 13:16 Steven Bosscher
     [not found] ` <003101c4d93c$8902e530$9641af83@tequila>
2004-12-03 15:12   ` [PATCH] Document target_fold_builtin Roger Sayle
2004-12-03 23:17   ` Richard Henderson
2004-12-03 23:16 ` Richard Henderson [this message]
2004-12-04  0:08 ` New and undocumented target hooks (cf. PR3386, a regression) Roger Sayle
2004-12-04  0:21   ` Eric Botcazou
2004-12-04  0:26   ` Richard Henderson
2004-12-06 19:47 ` Dorit Naishlos
2004-12-06 20:52   ` Richard Henderson
2004-12-07 16:09     ` Dorit Naishlos
2004-12-07 17:50       ` Richard Henderson

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=20041203231514.GC22293@redhat.com \
    --to=rth@redhat.com \
    --cc=bonzini@gnu.org \
    --cc=dorit@il.ibm.com \
    --cc=echristo@redhat.com \
    --cc=fjahanian@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kkojima@gcc.gnu.org \
    --cc=roger@eyesopen.com \
    --cc=stevenb@suse.de \
    --cc=zack@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).