From: Clifford E. Cummings (cliffc@sunburst-design.com)
Date: Mon Mar 02 1998 - 00:39:50 PST
BAD MSG:
Tom, Mac -
-Lines: 92
Content-Type: text/plain; charset="us-ascii"
Content-Length: 4485
X-Status: $$$$
X-UID: 0000000330
Status: RO
We have been accused of dogging it in the BTF by Stu ;-)
Could you gents each send out copies of your latest proposals for File I/O
enhancements and Signed Arithmetic to Drew and Stu?
Just a heads-up to Stu and Maq, the BTF plans to present both the File I/O
and Signed Arithmetic enhancements to the entire VSG on Tuesday, just to
introduce the VSG to the proposals we are making. After our last conference
call on Monday, we decided that we did not meet the 2-week qualification
period to ask for a vote on the two proposals at the next VSG.
I also hope to have a fairly stable enhanced BNF ready by Monday for
distribution. I have spent more than a little time trying to dial all of
the enhancement proposals into the BNF (and in the process found more BNF
errata including significant problems with the BNF for functions -
statements include tasks and timing controls - not legal in functions).
To more fully experience this level of fun, I think the PLI task force
should put together the BNF for the entire PLI/VPI (Stu to implement ;-)
Regards - Cliff
At 05:57 PM 3/3/98 -0800, you wrote:
>At 08:50 AM 3/2/98 -0800, you wrote:
>>
>>I thought all proposals had to be circulated two weeks before any voting
>>could occur. I thought Drew was the person who vigorously proposed this
>>restriction (when Steve Wadsworth tried to vote on a proposal that had only
>>been circulated for one week).
>>
>>Comments?
>>
>>- Cliff
>>
>
>Cliff,
>
>I've added Steve and Maq to your message list, since your question affects
>all of the task force chairs -- especially as we draw near the deadlines to
>have a 1998 Verilog standard.
>
>I'm not sure if Maq decided on two weeks notice or just one week. But
>here's the real reasons I sent the vote message:
>
>1. When I finally got back from all my travels and went through my
>countless numbers of 1364 core and BTF messages, I saw no indication that
>any other task force, including the BTF, had any thing at all to vote on
>next week. Though it was only 8 days before the 1364 VSG meeting, I
>thought I'd save Maq the embarrassment of holding a meeting with nothing to
>do :) Actually, my last-second trip out of town all last week simply
>didn't give me a chance to prepare and mail the vote review message any
>sooner.
>
>2. Since there are no other proposals to vote on, one week ought to be
>plenty of time for the 1364 members to review the 15 rather simple PLI task
>force actions.
>
>3. Advance notice has yet to have any real impact -- very few 1364 core
>members read the action items prior to the meeting anyway.
>
>4. At the 1364 VSG meeting, you or anyone else can request to delay the
>vote on the PLI actions because one week, or longer if you so feel, was not
>enough time. it's happened in the past, and we have been happy to withdraw
>one or more items for additional review and a later vote.
>
>Please take note: The PLI task force is very near a total impasse, because
>much of what we have left to do is dependent on your task force and Steve's
>task force finalizing your changes to the language. Since it appears that
>neither of you plan to have proposals ready until the mid-May meeting at
>the earliest, it will be difficult (impossible?) for the PLI task force to
>meet the goal of a 1998 standard (we will need several weeks EACH for some
>of the major changes you are discussing).
>
>Speaking strictly for myself, I would much rather see some well-prepared,
>final draft proposals from you and Steve that came with short notice, than
>sit and wait and wonder until next May. Even if the 1364 VSG vote on the
>proposals gets postponed due to short notice, at least the PLI task force
>would have the final draft to work from. So far, the only proposal I've
>seen that is far enough along for the PLI task force to use is the File I/O
>proposal, which happens to have relatively minor impact on the PLI.
>
>Stu
<p>//********************************************************************//
// Cliff Cummings E-mail: cliffc@sunburst-design.com //
// Sunburst Design Phone: 503-579-6362 / FAX: 503-579-7631 //
// 15870 SW Breccia Dr., Beaverton, OR 97007 //
// //
// Verilog & Synthesis Training / On-Site Training //
// Verilog, VHDL, Synopsys, LMG, FPGA, Consulting and Contracting //
//********************************************************************//
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:52:46 PDT
and
sponsored by Boyd Technology, Inc.