From: David Daney <ddaney@avtrex.com>
To: gcc-patches@gcc.gnu.org
Subject: [Patch] 4/3 i386 target support for __builtin___clear_cache()
Date: Thu, 05 Jul 2007 09:05:00 -0000 [thread overview]
Message-ID: <468CA28A.1040204@avtrex.com> (raw)
In-Reply-To: <468734D3.3020908@avtrex.com>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
This patch adds support for __builtin___clear_cache() to the i386 (and
x86_64) target.
There is not much to see here. All I do is define the
TARGET_BUILTIN_CLEAR_CACHE_INLINE_P target hook to always return false.
This causes __builtin___clear_cache() to be a nop for this target.
Tested with bootstrap and make -k check with no regressions on
x86_64-unknown-linux-gnu.
OK to commit if the target independent portion of the patch is approved?
2007-07-04 David Daney <ddaney@avtrex.com>
* config/i386/i386.h (TARGET_BUILTIN_CLEAR_CACHE_INLINE_P): Define
target hook.
[-- Attachment #2: flush-cache4.diff --]
[-- Type: text/x-patch, Size: 672 bytes --]
Index: config/i386/i386.h
===================================================================
--- config/i386/i386.h (revision 125997)
+++ config/i386/i386.h (working copy)
@@ -1716,6 +1716,12 @@ typedef struct ix86_args {
#define INITIALIZE_TRAMPOLINE(TRAMP, FNADDR, CXT) \
x86_initialize_trampoline ((TRAMP), (FNADDR), (CXT))
+
+/* We never need to clear the instruction cache. Returning true will
+ prevent _builtin__clear_cache from expanding to a library call.
+ Since a "clear_cache" insn is not defined it will expand to
+ const0_rtx. */
+#define TARGET_BUILTIN_CLEAR_CACHE_INLINE_P hook_bool_void_true
\f
/* Definitions for register eliminations.
next prev parent reply other threads:[~2007-07-05 7:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 5:01 [Patch] 1/3 Add new builtin __builtin_flush_icache() David Daney
2007-07-01 5:05 ` [Patch] 2/3 MIPS support for " David Daney
2007-07-01 10:56 ` Richard Sandiford
2007-07-05 7:50 ` David Daney
2007-07-05 19:05 ` Richard Sandiford
2007-07-08 20:00 ` David Daney
2007-07-09 19:07 ` Richard Sandiford
2007-07-11 5:45 ` David Daney
2007-07-01 5:11 ` [Patch] 3/3 FFI: Use __builtin_flush_icache() to flush MIPS i-cache David Daney
2007-07-05 8:34 ` David Daney
2007-07-05 19:08 ` Richard Sandiford
2007-07-11 18:55 ` Tom Tromey
2007-07-01 8:01 ` [Patch] 1/3 Add new builtin __builtin_flush_icache() Paolo Bonzini
2007-07-01 17:51 ` Thiemo Seufer
2007-07-01 18:47 ` David Daney
2007-07-02 5:04 ` Paolo Bonzini
2007-07-03 23:55 ` Mark Mitchell
2007-07-04 7:18 ` Paolo Bonzini
2007-07-04 17:17 ` Mark Mitchell
2007-07-04 17:10 ` David Daney
2007-07-04 17:51 ` Mark Mitchell
2007-07-05 7:36 ` David Daney
2007-07-05 17:59 ` Richard Sandiford
2007-07-05 18:23 ` David Daney
2007-07-05 19:11 ` Richard Sandiford
2007-07-06 6:07 ` Mark Mitchell
2007-07-06 6:19 ` David Daney
2007-07-06 16:39 ` Mark Mitchell
2007-07-08 19:22 ` David Daney
2007-07-09 19:04 ` Richard Sandiford
2007-07-11 2:22 ` Mark Mitchell
2007-07-11 4:47 ` David Daney
2007-07-05 9:05 ` David Daney [this message]
2007-07-08 20:39 ` [Patch] 4/3 i386 target support for __builtin___clear_cache() David Daney
[not found] <468734D3.3020908@avtrex.com.suse.lists.egcs-patches>
[not found] ` <468CA28A.1040204@avtrex.com.suse.lists.egcs-patches>
2007-07-05 10:30 ` Andi Kleen
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=468CA28A.1040204@avtrex.com \
--to=ddaney@avtrex.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).