Re: BTF enhancement open issues which Kurt thinks belong to datatypes

From: Shalom.Bresticker@freescale.com
Date: Thu May 06 2004 - 23:43:10 PDT

  • Next message: Kathy McKinley: "4-29 datatypes minutes"

    These are my opinions on the list Kurt submitted of enhancement requests which
    might properly be within the scope of the datatypes group.

    ISSUE
    # Synopsis
    ----------------------------
      2 Allow negative genvars

    No, already dealt with in generate proposal (#113)

      4 Allow assignment to an array

    Yes, within context of generalizing assignments to new data types

    55 allow arrays and reals as ports

    Yes, within context of generalizing ports to new data types

    58 allow force on memory word or bit-/part-select of vector variable

    Yes, within context of generalizing forces and procedural continuous assignments
    to new data types. Related to #4.

    61 add enumerated data type
    62 add record/structure data type

    Obviously

    183 allow reverse part-select [lsb:msb]

    No. Independent of data type.

    191 Add localparam to ANSI-type param list

    No, unless there are going to be significant extensions to parameters

    293 variable width floating point in Verilog 200X

    Yes

    297 Allow instance array connected to data array

    No. It seems to be independent of the datatype. As long as an array select is
    legal to connect to a port, and it already is, the form of instance arrays will
    work for all legal port types. Defining the legal port types is orthogonal to
    the form of instantiating instance arrays.

    298 Add field widths to print formats

    No, this is specific for printing integral data types.
    It is orthogonal to data type enhancements.

    357 Proposal for Extending Verilog Data Types

    Obviously.

    384 add mfactor parameters

    No.

    385 interconnect net that resolves to type

    Yes, but need more information.

    389 dynamic param

    Yes, but need more information.

    390 math functions

    No, this is not related to new datatypes.

    391 wreal type

    Yes, but already covered by Cadence proposal.

    400 reduce arithmetic operators x-pessimism
    401 reduce relational operators x-pessimism

    No, these 2 do not relate to new datatypes.

    404 add wildcards for equality operators
    405 add ranges for equality operators
    406 add lists for equality operators

    These 3, no.

    409 lists in part-selects

    No. Not related.

    411 extend operators to vectors and arrays

    Yes.

    414 rotate operator

    No.

    419 reconsider for 1364-2005 proposals made for 1364-2001

    No, let Priorities group look through them and find what is appropriate for
    datatypes, if any.

    450 Compressed Assignment Satements

    No.

    474 First class part selection operator

    No.

    478 Provide part selection of a structure

    Yes.

    498 system function/task to extract timescale info to variables

    No.

    502 Dynamic Values on attributes

    No.

    508 add arrays of `defines
    509 add arrays of parameters

    No.

    514 config file should support module and primitive arrays

    No, this is for a configuration group.

    519 system function to get signal strength

    No.

    520 3.3.2: deprecate "scalared" and "vectored" keywords

    No.

    532 new, binary dump format in addition to vcd

    No.

    537 allow unsized numbers and integer variables in concatenations

    No.

    545 4.2.1, 4.2.2: out of bounds addressing

    No.

    547 define size zero replication constant

    No.

    573 loops within concatenations?

    No.



    This archive was generated by hypermail 2.1.4 : Thu May 06 2004 - 23:24:01 PDT and
    sponsored by Boyd Technology, Inc.