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] Merge #1580
Date: Fri, 14 Oct 2022 15:58:47 +0000 (GMT)	[thread overview]
Message-ID: <20221014155847.91F07384BC3A@sourceware.org> (raw)

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

commit fa0bd801922d095893c9318ad1d0c78141c05796
Merge: c85492954de 6dca194d4b5
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Oct 14 14:41:18 2022 +0000

    Merge #1580
    
    1580: Add early name resolver r=CohenArthur a=CohenArthur
    
    This addresses our issue with name resolution (#1576) not acting on macros early enough but does not fix it yet.
    
    This name resolver performs the same macro name resolution as what was previously done by the AttrVisitor visitor and macro expander.
    
    It also resolves macro expressions in builtin-macros properly, as well as expanded AST nodes when necessary.
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/Make-lang.in                        |    1 +
 gcc/rust/ast/rust-path.h                     |   17 +
 gcc/rust/expand/rust-attribute-visitor.cc    |   10 -
 gcc/rust/expand/rust-macro-builtins.cc       |    9 +-
 gcc/rust/expand/rust-macro-expand.cc         |   30 +-
 gcc/rust/expand/rust-macro-expand.h          |    4 +
 gcc/rust/resolve/rust-ast-resolve-item.cc    |    8 +
 gcc/rust/resolve/rust-early-name-resolver.cc | 1087 ++++++++++++++++++++++++++
 gcc/rust/resolve/rust-early-name-resolver.h  |  210 +++++
 gcc/rust/rust-session-manager.cc             |    4 +
 gcc/rust/util/rust-hir-map.cc                |   22 +
 gcc/rust/util/rust-hir-map.h                 |    6 +
 12 files changed, 1373 insertions(+), 35 deletions(-)

                 reply	other threads:[~2022-10-14 15:58 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=20221014155847.91F07384BC3A@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).