[gcc r14-8564] gccrs: toplevel: Add comment about running the collector twice
Arthur Cohen
cohenarthur@gcc.gnu.org
Tue Jan 30 12:00:12 GMT 2024
https://gcc.gnu.org/g:0a5cc7a4cb2d379f17f75491fae8428dec901e1c
commit r14-8564-g0a5cc7a4cb2d379f17f75491fae8428dec901e1c
Author: Arthur Cohen <arthur.cohen@embecosm.com>
Date: Tue Aug 22 17:29:56 2023 +0200
gccrs: toplevel: Add comment about running the collector twice
gcc/rust/ChangeLog:
* resolve/rust-toplevel-name-resolver-2.0.cc
(TopLevel::insert_or_error_out): Add documentation comment.
(TopLevel::go): Likewise.
Diff:
---
gcc/rust/resolve/rust-toplevel-name-resolver-2.0.cc | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/gcc/rust/resolve/rust-toplevel-name-resolver-2.0.cc b/gcc/rust/resolve/rust-toplevel-name-resolver-2.0.cc
index fbded3e49e18..b9d0bc7c0ac9 100644
--- a/gcc/rust/resolve/rust-toplevel-name-resolver-2.0.cc
+++ b/gcc/rust/resolve/rust-toplevel-name-resolver-2.0.cc
@@ -43,6 +43,9 @@ TopLevel::insert_or_error_out (const Identifier &identifier, const T &node,
if (!result)
{
+ // can we do something like check if the node id is the same? if it is the
+ // same, it's not an error, just the resolver running multiple times?
+
rich_location rich_loc (line_table, loc);
rich_loc.add_range (node_locations[result.error ().existing]);
@@ -54,6 +57,11 @@ TopLevel::insert_or_error_out (const Identifier &identifier, const T &node,
void
TopLevel::go (AST::Crate &crate)
{
+ // we do not include builtin types in the top-level definition collector, as
+ // they are not used until `Late`. furthermore, we run this visitor multiple
+ // times in a row in a fixed-point fashion, so it would make the code
+ // responsible for this ugly and perfom a lot of error checking.
+
for (auto &item : crate.items)
item->accept_vis (*this);
}
More information about the Gcc-cvs
mailing list