luke
/
iverilog
mirror of https://github.com/steveicarus/iverilog.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
iverilog/pform_types.cc

78 lines
1.8 KiB
C++
Raw Normal View History

Rework the heirarchical identifier parse syntax and pform to handle more general combinations of heirarch and bit selects.
2007-05-24 06:07:11 +02:00
/*
Create new base class for all named items that can be added to a scope. Provide a helper function to identify the derived classes when reporting errors.
2019-09-24 00:17:31 +02:00
* Copyright (c) 2007-2019 Stephen Williams (steve@icarus.com)
Rework the heirarchical identifier parse syntax and pform to handle more general combinations of heirarch and bit selects.
2007-05-24 06:07:11 +02:00
*
* This source code is free software; you can redistribute it
* and/or modify it in source code form under the terms of the GNU
* General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option)
* any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
updated FSF-address
2012-08-29 03:41:23 +02:00
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
Rework the heirarchical identifier parse syntax and pform to handle more general combinations of heirarch and bit selects.
2007-05-24 06:07:11 +02:00
*/
# include "pform_types.h"
Parse simple typedefs Parse typedefs with structs and enums, but give a sorry message, because they are not yet supported. Rearrange some of the parse rules for variables in order to increase comonality with the typedef rules.
2012-01-08 00:37:30 +01:00
data_type_t::~data_type_t()
{
}
First pass at getting strings to work. In vvp, create the .var/str variable for representing strings, and handle strings in the $display system task. Add to vvp threads the concept of a stack of strings. This is going to be how complex objects are to me handled in the future: forth-like operation stacks. Also add the first two instructions to minimally get strings to work. In the parser, handle the variable declaration and make it available to the ivl_target.h code generator. The vvp code generator can use this information to generate the code for new vvp support.
2012-06-18 03:22:50 +02:00
Create new base class for all named items that can be added to a scope. Provide a helper function to identify the derived classes when reporting errors.
2019-09-24 00:17:31 +02:00
PNamedItem::SymbolType data_type_t::symbol_type() const
{
return TYPE;
}
First pass at getting strings to work. In vvp, create the .var/str variable for representing strings, and handle strings in the $display system task. Add to vvp threads the concept of a stack of strings. This is going to be how complex objects are to me handled in the future: forth-like operation stacks. Also add the first two instructions to minimally get strings to work. In the parser, handle the variable declaration and make it available to the ivl_target.h code generator. The vvp code generator can use this information to generate the code for new vvp support.
2012-06-18 03:22:50 +02:00
string_type_t::~string_type_t()
{
}
Clean up PWire handling of wire data type. / Reword packed type handling
2012-08-03 05:14:55 +02:00
ivl_variable_type_t data_type_t::figure_packed_base_type(void) const
{
return IVL_VT_NO_TYPE;
}
ivl_variable_type_t parray_type_t::figure_packed_base_type(void) const
{
return base_type->figure_packed_base_type();
}
ivl_variable_type_t vector_type_t::figure_packed_base_type(void) const
{
return base_type;
}
Elaborate foreach loops as synthetic for loops. Create an implicit scope to hold the index variable, and generate a for loop to perform the functionality of the foreach.
2014-08-22 00:47:46 +02:00
Fix base type for nested types with enum or atom2 sub-types To determine the base type structs and packed arrays call the figure_packed_base_type() for their sub-types. This method is not defined for enum or atom2 types and the default implementation returns IVL_VT_NO_TYPE. As a result packed arrays of enum or atom2 types and packed structs with members of enum or atom2 types get elaborated with IVL_VT_NO_TYPE as the base type. For example ``` struct packed { bit signed [31:0] x; } s1; ``` gets elaborated with a base type of IVL_VT_BOOL, while ``` struct packed { int x; } s2; ``` gets elaborated with a base type of IVL_VT_NONE. To fix this define the figure_packed_base_type() for enum_type_t and atom2_type_t. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-01-08 14:20:35 +01:00
ivl_variable_type_t enum_type_t::figure_packed_base_type() const
{
Support type identifier base type for enum The base type for an enum type can be a type identifier for a typedef as long as it resolves to a vector or integer type with at most one packed dimension. This is described in section 6.19 ("Enumerations") of the LRM (1800-2017). E.g. ``` typedef bit [3:0] T; enum T { A } e; ``` Add support for this by allowing to specify a type identifier as the base type for an enum in the parser. During elaboration it is checked whether the type identifier resolves to a valid enum base type. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-03-15 08:24:33 +01:00
return base_type->figure_packed_base_type();
Fix base type for nested types with enum or atom2 sub-types To determine the base type structs and packed arrays call the figure_packed_base_type() for their sub-types. This method is not defined for enum or atom2 types and the default implementation returns IVL_VT_NO_TYPE. As a result packed arrays of enum or atom2 types and packed structs with members of enum or atom2 types get elaborated with IVL_VT_NO_TYPE as the base type. For example ``` struct packed { bit signed [31:0] x; } s1; ``` gets elaborated with a base type of IVL_VT_BOOL, while ``` struct packed { int x; } s2; ``` gets elaborated with a base type of IVL_VT_NONE. To fix this define the figure_packed_base_type() for enum_type_t and atom2_type_t. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-01-08 14:20:35 +01:00
}
Correctly handle separate port type declaration for `integer` and `time` When using non-ANSI style port declarations it is possible to declare the port direction and the data type for the port in separate statements. E.g. ``` input x; reg x; ``` When using packed array dimensions they must match for both declarations. E.g. ``` input [3:0] x; reg [3:0] x; ``` But this only applies for vector types, i.e. the packed dimension is explicitly declared. It does not apply to the `integer` and `time` types, which have an implicit packed dimension. The current implementation requires that even for `integer` and `time` types the implicit dimension needs to be explicitly declared in the port direction. E.g. the following will result in a elaboration error complaining about a packed dimension mismatch. ``` module test; output x; integer x; endmodule ``` Currently the parser creates a vector_type_t for `time` and `integer`. This means that e.g. `time` and `reg [63:0]` are indistinguishable during elaboration, even though they require different behavior. To fix let the atom2_type_t handle `integer` and `time`. Since it no longer exclusively handles 2-state types, rename it to atom_type_t. This also fixes a problem with the vlog95 target unit tests. The vlog95 target translates ``` module test(output integer x); endmodule ``` to ``` module test(x); output x; integer x; endmodule ``` which then fails when being elaborated again. There were some regression tests that were failing because of this that will now pass. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-03-12 21:10:19 +01:00
ivl_variable_type_t atom_type_t::figure_packed_base_type() const
Fix base type for nested types with enum or atom2 sub-types To determine the base type structs and packed arrays call the figure_packed_base_type() for their sub-types. This method is not defined for enum or atom2 types and the default implementation returns IVL_VT_NO_TYPE. As a result packed arrays of enum or atom2 types and packed structs with members of enum or atom2 types get elaborated with IVL_VT_NO_TYPE as the base type. For example ``` struct packed { bit signed [31:0] x; } s1; ``` gets elaborated with a base type of IVL_VT_BOOL, while ``` struct packed { int x; } s2; ``` gets elaborated with a base type of IVL_VT_NONE. To fix this define the figure_packed_base_type() for enum_type_t and atom2_type_t. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-01-08 14:20:35 +01:00
{
Correctly handle separate port type declaration for `integer` and `time` When using non-ANSI style port declarations it is possible to declare the port direction and the data type for the port in separate statements. E.g. ``` input x; reg x; ``` When using packed array dimensions they must match for both declarations. E.g. ``` input [3:0] x; reg [3:0] x; ``` But this only applies for vector types, i.e. the packed dimension is explicitly declared. It does not apply to the `integer` and `time` types, which have an implicit packed dimension. The current implementation requires that even for `integer` and `time` types the implicit dimension needs to be explicitly declared in the port direction. E.g. the following will result in a elaboration error complaining about a packed dimension mismatch. ``` module test; output x; integer x; endmodule ``` Currently the parser creates a vector_type_t for `time` and `integer`. This means that e.g. `time` and `reg [63:0]` are indistinguishable during elaboration, even though they require different behavior. To fix let the atom2_type_t handle `integer` and `time`. Since it no longer exclusively handles 2-state types, rename it to atom_type_t. This also fixes a problem with the vlog95 target unit tests. The vlog95 target translates ``` module test(output integer x); endmodule ``` to ``` module test(x); output x; integer x; endmodule ``` which then fails when being elaborated again. There were some regression tests that were failing because of this that will now pass. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-03-12 21:10:19 +01:00
switch (type_code) {
case TIME:
case INT:
return IVL_VT_LOGIC;
default:
return IVL_VT_BOOL;
}
Fix base type for nested types with enum or atom2 sub-types To determine the base type structs and packed arrays call the figure_packed_base_type() for their sub-types. This method is not defined for enum or atom2 types and the default implementation returns IVL_VT_NO_TYPE. As a result packed arrays of enum or atom2 types and packed structs with members of enum or atom2 types get elaborated with IVL_VT_NO_TYPE as the base type. For example ``` struct packed { bit signed [31:0] x; } s1; ``` gets elaborated with a base type of IVL_VT_BOOL, while ``` struct packed { int x; } s2; ``` gets elaborated with a base type of IVL_VT_NONE. To fix this define the figure_packed_base_type() for enum_type_t and atom2_type_t. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-01-08 14:20:35 +01:00
}
Correctly handle separate port type declaration for `integer` and `time` When using non-ANSI style port declarations it is possible to declare the port direction and the data type for the port in separate statements. E.g. ``` input x; reg x; ``` When using packed array dimensions they must match for both declarations. E.g. ``` input [3:0] x; reg [3:0] x; ``` But this only applies for vector types, i.e. the packed dimension is explicitly declared. It does not apply to the `integer` and `time` types, which have an implicit packed dimension. The current implementation requires that even for `integer` and `time` types the implicit dimension needs to be explicitly declared in the port direction. E.g. the following will result in a elaboration error complaining about a packed dimension mismatch. ``` module test; output x; integer x; endmodule ``` Currently the parser creates a vector_type_t for `time` and `integer`. This means that e.g. `time` and `reg [63:0]` are indistinguishable during elaboration, even though they require different behavior. To fix let the atom2_type_t handle `integer` and `time`. Since it no longer exclusively handles 2-state types, rename it to atom_type_t. This also fixes a problem with the vlog95 target unit tests. The vlog95 target translates ``` module test(output integer x); endmodule ``` to ``` module test(x); output x; integer x; endmodule ``` which then fails when being elaborated again. There were some regression tests that were failing because of this that will now pass. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-03-12 21:10:19 +01:00
atom_type_t size_type (atom_type_t::INT, true);
Create new base class for all named items that can be added to a scope. Provide a helper function to identify the derived classes when reporting errors.
2019-09-24 00:17:31 +02:00
PNamedItem::SymbolType enum_type_t::symbol_type() const
{
return ENUM;
}
PNamedItem::SymbolType class_type_t::symbol_type() const
{
return CLASS;
}