From: Ian Lance Taylor <iant@google.com>
To: "Anatoly Sokolov" <aesok@post.ru>
Cc: <gcc-patches@gcc.gnu.org>, <rth@redhat.com>,
<chertykov@gmail.com>, "Andy H" <hutchinsonandy@aim.com>
Subject: Re: Add more restriction in 'peep2_find_free_register'
Date: Mon, 30 Jun 2008 21:02:00 -0000 [thread overview]
Message-ID: <m3skuusklz.fsf@google.com> (raw)
In-Reply-To: <EA53E23276F34EEEBE5A233BC7DC9364@Vista> (Anatoly Sokolov's message of "Thu\, 19 Jun 2008 19\:35\:22 +0400")
"Anatoly Sokolov" <aesok@post.ru> writes:
> 2008-06-19 Anatoly Sokolov <aesok@post.ru>
>
> * target.h (struct gcc_target): Add hard_regno_scratch_ok field.
> * target-def.h (TARGET_HARD_REGNO_SCRATCH_OK): New.
> (TARGET_INITIALIZER): Use TARGET_HARD_REGNO_SCRATCH_OK.
> * targhooks.c (default_hard_regno_scratch_ok): New function.
> * targhooks.h (default_hard_regno_scratch_ok): Declare function.
> * doc/tm.texi: Document TARGET_HARD_REGNO_SCRATCH_OK hook.
> * recog.c (peep2_find_free_register): Add check for global regs.
> Add target specific check.
> +@deftypefn {Target Hook} bool TARGET_HARD_REGNO_SCRATCH_OK (unsigned int @var{regno})
> +This target hook should return 'true' if it is OK to use a hard register
> +@var{regno} as scratch reg in peephole2.
> +
> +One common use of this macro is to prevent using of a register that
> +is not saved by a prologue in an interrupt handler.
> +
> +TThe default version of this hook always returns 'true'.
> +@end deftypefn
Change 'true' => @code{true}, in two places.
Typo: "TThe" => "The".
This patch is OK with those changes.
Thanks.
Ian
next prev parent reply other threads:[~2008-06-30 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 22:26 Anatoly Sokolov
2008-06-18 14:47 ` Ian Lance Taylor
2008-06-19 15:36 ` Anatoly Sokolov
2008-06-30 21:02 ` Ian Lance Taylor [this message]
2008-06-18 22:10 Anatoly Sokolov
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=m3skuusklz.fsf@google.com \
--to=iant@google.com \
--cc=aesok@post.ru \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hutchinsonandy@aim.com \
--cc=rth@redhat.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).