Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
Pyston
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
Pyston
Commits
138433d8
Commit
138433d8
authored
Nov 04, 2016
by
Marius Wachtler
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add back an assert which I accidentally removed in the BST change
parent
defc3153
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
0 deletions
+9
-0
src/codegen/irgen.cpp
src/codegen/irgen.cpp
+9
-0
No files found.
src/codegen/irgen.cpp
View file @
138433d8
...
@@ -359,6 +359,15 @@ protected:
...
@@ -359,6 +359,15 @@ protected:
(
*
sym_table
)[
*
vreg
]
=
NULL
;
(
*
sym_table
)[
*
vreg
]
=
NULL
;
return
false
;
return
false
;
}
}
bool
visit_storename
(
BST_StoreName
*
node
)
override
{
InternedString
name
=
getCodeConstants
().
getInternedString
(
node
->
index_id
);
assert
(
name
.
c_str
()[
0
]
==
'#'
);
// it must be a temporary
// You might think I need to check whether `name' is being assigned globally or locally,
// since a global assign doesn't affect the symbol table. However, the CFG pass only
// generates invoke-assigns to temporary variables. Just to be sure, we assert:
assert
(
node
->
lookup_type
!=
ScopeInfo
::
VarScopeType
::
GLOBAL
);
return
false
;
}
public:
public:
static
std
::
pair
<
SymbolTable
*
,
bool
/* created_new_sym_table */
>
static
std
::
pair
<
SymbolTable
*
,
bool
/* created_new_sym_table */
>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment