public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] Use more conservative fences on RISC-V
@ 2017-03-17 22:56 Palmer Dabbelt
  2017-03-20 16:43 ` Palmer Dabbelt
  0 siblings, 1 reply; 2+ messages in thread
From: Palmer Dabbelt @ 2017-03-17 22:56 UTC (permalink / raw)
  To: gcc-patches; +Cc: Palmer Dabbelt

The RISC-V memory model is still in the process of being formally
specified, so for now we're going to be safe and add the I/O bits to
userspace fences because there's no way to know if userspace is touching
memory-mapped I/O regions at compile time.

This will have no impact on existing microarchitecutres because they
treat all fences conservatively.

gcc/ChangeLog:

2017-03-17  Palmer Dabbelt  <palmer@dabbelt.com>

        * config/riscv/riscv.c (riscv_print_operand): Use "fence
        iorw,ow".
        * config/riscv/sync.mc (mem_thread_fence_1): Use "fence
        iorw,iorw".
---
 gcc/ChangeLog            | 7 +++++++
 gcc/config/riscv/riscv.c | 2 +-
 gcc/config/riscv/sync.md | 2 +-
 3 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 3e108dd..de32689 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,10 @@
+2017-03-17  Palmer Dabbelt  <palmer@dabbelt.com>
+
+	* config/riscv/riscv.c (riscv_print_operand): Use "fence
+	iorw,ow".
+	* config/riscv/sync.mc (mem_thread_fence_1): Use "fence
+	iorw,iorw".
+
 2017-03-17  Palmer Dabbelt  <palmer@dabbelt.com
 
 	* doc/install.texi (Specific) <riscv32-*-elf>: Add riscv32-*-elf,
diff --git a/gcc/config/riscv/riscv.c b/gcc/config/riscv/riscv.c
index 25cc803..fa93c3c 100644
--- a/gcc/config/riscv/riscv.c
+++ b/gcc/config/riscv/riscv.c
@@ -2794,7 +2794,7 @@ riscv_print_operand (FILE *file, rtx op, int letter)
 
     case 'F':
       if (riscv_memmodel_needs_release_fence ((enum memmodel) INTVAL (op)))
-	fputs ("fence rw,w; ", file);
+	fputs ("fence iorw,ow; ", file);
       break;
 
     default:
diff --git a/gcc/config/riscv/sync.md b/gcc/config/riscv/sync.md
index 09970b9..cde19e3 100644
--- a/gcc/config/riscv/sync.md
+++ b/gcc/config/riscv/sync.md
@@ -53,7 +53,7 @@
 	(unspec:BLK [(match_dup 0)] UNSPEC_MEMORY_BARRIER))
    (match_operand:SI 1 "const_int_operand" "")] ;; model
   ""
-  "fence\trw,rw")
+  "fence\tiorw,iorw")
 
 ;; Atomic memory operations.
 
-- 
2.10.2

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] Use more conservative fences on RISC-V
  2017-03-17 22:56 [PATCH] Use more conservative fences on RISC-V Palmer Dabbelt
@ 2017-03-20 16:43 ` Palmer Dabbelt
  0 siblings, 0 replies; 2+ messages in thread
From: Palmer Dabbelt @ 2017-03-20 16:43 UTC (permalink / raw)
  To: gcc-patches

On Fri, 17 Mar 2017 15:52:54 PDT (-0700), Palmer Dabbelt wrote:
> The RISC-V memory model is still in the process of being formally
> specified, so for now we're going to be safe and add the I/O bits to
> userspace fences because there's no way to know if userspace is touching
> memory-mapped I/O regions at compile time.
>
> This will have no impact on existing microarchitecutres because they
> treat all fences conservatively.
>
> gcc/ChangeLog:
>
> 2017-03-17  Palmer Dabbelt  <palmer@dabbelt.com>
>
>         * config/riscv/riscv.c (riscv_print_operand): Use "fence
>         iorw,ow".
>         * config/riscv/sync.mc (mem_thread_fence_1): Use "fence
>         iorw,iorw".
> ---
>  gcc/ChangeLog            | 7 +++++++
>  gcc/config/riscv/riscv.c | 2 +-
>  gcc/config/riscv/sync.md | 2 +-
>  3 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/gcc/ChangeLog b/gcc/ChangeLog
> index 3e108dd..de32689 100644
> --- a/gcc/ChangeLog
> +++ b/gcc/ChangeLog
> @@ -1,3 +1,10 @@
> +2017-03-17  Palmer Dabbelt  <palmer@dabbelt.com>
> +
> +	* config/riscv/riscv.c (riscv_print_operand): Use "fence
> +	iorw,ow".
> +	* config/riscv/sync.mc (mem_thread_fence_1): Use "fence
> +	iorw,iorw".
> +
>  2017-03-17  Palmer Dabbelt  <palmer@dabbelt.com
>
>  	* doc/install.texi (Specific) <riscv32-*-elf>: Add riscv32-*-elf,
> diff --git a/gcc/config/riscv/riscv.c b/gcc/config/riscv/riscv.c
> index 25cc803..fa93c3c 100644
> --- a/gcc/config/riscv/riscv.c
> +++ b/gcc/config/riscv/riscv.c
> @@ -2794,7 +2794,7 @@ riscv_print_operand (FILE *file, rtx op, int letter)
>
>      case 'F':
>        if (riscv_memmodel_needs_release_fence ((enum memmodel) INTVAL (op)))
> -	fputs ("fence rw,w; ", file);
> +	fputs ("fence iorw,ow; ", file);
>        break;
>
>      default:
> diff --git a/gcc/config/riscv/sync.md b/gcc/config/riscv/sync.md
> index 09970b9..cde19e3 100644
> --- a/gcc/config/riscv/sync.md
> +++ b/gcc/config/riscv/sync.md
> @@ -53,7 +53,7 @@
>  	(unspec:BLK [(match_dup 0)] UNSPEC_MEMORY_BARRIER))
>     (match_operand:SI 1 "const_int_operand" "")] ;; model
>    ""
> -  "fence\trw,rw")
> +  "fence\tiorw,iorw")
>
>  ;; Atomic memory operations.

Committed.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-03-20 16:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-17 22:56 [PATCH] Use more conservative fences on RISC-V Palmer Dabbelt
2017-03-20 16:43 ` Palmer Dabbelt

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).