public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] moved operator.h to util/rust-operators.h
Date: Mon, 30 Jan 2023 13:24:33 +0000 (GMT)	[thread overview]
Message-ID: <20230130132433.B072D3858C2C@sourceware.org> (raw)

https://gcc.gnu.org/g:e66cb001dc7a011a27c8104f9a9dd7ee6c9a6c08

commit e66cb001dc7a011a27c8104f9a9dd7ee6c9a6c08
Author: Abdul Rafey <abdulrafeyq@gmail.com>
Date:   Sun Jan 29 16:59:17 2023 +0530

    moved operator.h to util/rust-operators.h
    
    Signed-off-by: Abdul Rafey <abdulrafeyq@gmail.com>

Diff:
---
 gcc/rust/ast/rust-ast.cc                       | 2 +-
 gcc/rust/ast/rust-expr.h                       | 2 +-
 gcc/rust/hir/tree/rust-hir-expr.h              | 2 +-
 gcc/rust/rust-backend.h                        | 2 +-
 gcc/rust/util/rust-lang-item.h                 | 2 +-
 gcc/rust/{operator.h => util/rust-operators.h} | 0
 6 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/gcc/rust/ast/rust-ast.cc b/gcc/rust/ast/rust-ast.cc
index c98df5106ef..813c35b7334 100644
--- a/gcc/rust/ast/rust-ast.cc
+++ b/gcc/rust/ast/rust-ast.cc
@@ -25,7 +25,7 @@ along with GCC; see the file COPYING3.  If not see
 #include "rust-session-manager.h"
 #include "rust-lex.h"
 #include "rust-parse.h"
-#include "operator.h"
+#include "rust-operators.h"
 
 /* Compilation unit used for various AST-related functions that would make
  * the headers too long if they were defined inline and don't receive any
diff --git a/gcc/rust/ast/rust-expr.h b/gcc/rust/ast/rust-expr.h
index 34bc6993ab6..3ed1885d5af 100644
--- a/gcc/rust/ast/rust-expr.h
+++ b/gcc/rust/ast/rust-expr.h
@@ -3,7 +3,7 @@
 
 #include "rust-ast.h"
 #include "rust-path.h"
-#include "operator.h"
+#include "rust-operators.h"
 
 namespace Rust {
 namespace AST {
diff --git a/gcc/rust/hir/tree/rust-hir-expr.h b/gcc/rust/hir/tree/rust-hir-expr.h
index 693704e538a..2c32d284e15 100644
--- a/gcc/rust/hir/tree/rust-hir-expr.h
+++ b/gcc/rust/hir/tree/rust-hir-expr.h
@@ -23,7 +23,7 @@
 #include "rust-ast-full-decls.h"
 #include "rust-hir.h"
 #include "rust-hir-path.h"
-#include "operator.h"
+#include "rust-operators.h"
 
 namespace Rust {
 namespace HIR {
diff --git a/gcc/rust/rust-backend.h b/gcc/rust/rust-backend.h
index cda264233b1..7a51f5fe2ef 100644
--- a/gcc/rust/rust-backend.h
+++ b/gcc/rust/rust-backend.h
@@ -26,7 +26,7 @@
 #include "rust-location.h"
 #include "rust-linemap.h"
 #include "rust-diagnostics.h"
-#include "operator.h"
+#include "util/rust-operators.h"
 #include "tree.h"
 
 // Pointers to these types are created by the backend, passed to the
diff --git a/gcc/rust/util/rust-lang-item.h b/gcc/rust/util/rust-lang-item.h
index 1aa5794df4e..52f53fa3f93 100644
--- a/gcc/rust/util/rust-lang-item.h
+++ b/gcc/rust/util/rust-lang-item.h
@@ -17,7 +17,7 @@
 // <http://www.gnu.org/licenses/>.
 
 #include "rust-system.h"
-#include "operator.h"
+#include "rust-operators.h"
 
 namespace Rust {
 namespace Analysis {
diff --git a/gcc/rust/operator.h b/gcc/rust/util/rust-operators.h
similarity index 100%
rename from gcc/rust/operator.h
rename to gcc/rust/util/rust-operators.h

                 reply	other threads:[~2023-01-30 13:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230130132433.B072D3858C2C@sourceware.org \
    --to=tschwinge@gcc.gnu.org \
    --cc=gcc-cvs@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).