Re: Configs proposal version #1

From: Adam Krolnik (krolnik@lsil.com)
Date: Tue May 03 2005 - 10:07:28 PDT

  • Next message: Shalom.Bresticker@freescale.com: "Mantis #658 for V-1364: Notes"

    Hi Cliff;

    Since we're making clarifications and changes together, why don't we address the
    remaining issues that people frequently ask for clarification...

    1. What kind of comments are accepted in library files and config blocks?
        (Presumably now that configuration blocks can be within verilog files
         that both line and region comments are applicable (I.e. // line and /* region */
         comments respectively)

    E.g. for library files...

       Within a library definition,

        library test_lib design//block/rtl/*.v ; (legal pathname)
        library another_lib design/*/rtl*/*.v ; (expands all directories)

       Are these valid library definitions, or a syntax errors because they parse as:

        'library' 'test_lib' 'design/' (rest is a comment)

        'library' 'another_lib' 'design*.v' ';' (lost the text '/*rtl*/'

       Ideally, I'd prefer not to have to embed path specifications in quotes. After all this
       file is FOR specifying filesystem paths, not strings...

    2. Can I have preprocessor definitions preprocessor statements in a library file?
        I might not be able to compile my files other than making a file with just the
       E.g.

         `define DESIGN1_CONFIG 4
         `define DESIGN2_WIDTH 12
         `define DESIGN_OPTSPEED

         library RTLlib design/*/`RTLPATH/*.v;

       E.g.

         library RTLlib design/*/rtl/*.v;

         `ifdef VER20
            include /path/ip/block/2.0/lib.map;
         `else
            include /path/ip/block/1.0/lib.map;
         `endif

    3. If parsers can be forgiving on the need for semicolons, can't we as writers of the
       LRM be somewhat forgiving too? I.e. why can't we keep or suggest optional semicolons?

    4. How about a few more examples for library map files ?
        There are only 2 examples (almost the same.)

    5. It would be nice to exclude a file from being included in a wildcarded file_path
        specification. The only way I have seen/used is the following:

         library DONT_USE_THIS_FILE design/my/bad/old/design/files/x_old.v;

         library RTLlib design/...;

    Thanks for doing the work Cliff! 

    -- 
     Adam Krolnik
     ZSP Verification Mgr.
     LSI Logic Corp.
     Plano TX. 75074
     Co-author "Assertion-Based Design"

    This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 09:43:35 PDT and
    sponsored by Boyd Technology, Inc.