ruby: fix slicc compiler to complain about duplicate symbols
Review Request #1924 - Created June 13, 2013 and submitted
| Information | |
|---|---|
| Lena Olson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 9756:4793fa5955e0 --------------------------- ruby: fix slicc compiler to complain about duplicate symbols Previously, .sm files were allowed to use the same name for a type and a variable. This is unnecessarily confusing and has some bad side effects, like not being able to declare later variables in the same scope with the same type. This causes the compiler to complain and die on things like Address Address.
util/regress --builds="ALPHA_MOESI_hammer,ALPHA_MESI_CMP_directory,ALPHA_MOESI_CMP_directory,ALPHA_MOESI_CMP_token,X86_MESI_CMP_directory" --compile-variants="debug" after application of Changeset 9756:8956d858a9e6 (review request 1921).
Posted (June 13, 2013, 8:43 a.m.)
-
src/mem/protocol/MOESI_CMP_token-L1cache.sm (Diff revision 1) -
I think all changes to this file should be merged with the other patch.
-
src/mem/slicc/symbols/SymbolTable.py (Diff revision 1) -
If I understand this correctly, what you are saying that only frame 0 needs to be checked. Why is not possible that other frames have a symbol the 'id' of which clashes with the 'id' you just got?
-
src/mem/slicc/symbols/SymbolTable.py (Diff revision 1) -
It seems like this statement will allow you to override an earlier declared type with a newly declared type. Is this intentional?
Review request changed
Updated (June 18, 2013, 11:49 a.m.)
Description: |
|
|||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+5) |
