Neil, Was the Pre-postponed region also added to the bulleted list that serves as the third paragraph of 15.3? I didn't see that in the proposal for 712. In the paragraph about the Postponed region, I believe that the "Observe" region should actually be the "Observed" region. In the NOTE attached to the paragraph about the Post-observed region, the spelling of "schcedule" should be corrected. In the paragraph after that, should "Pre-Postponed" be written as "Pre-postponed" instead for consistency with other regions that have prefixed names? I.e., don't capitalize the first "P" in the suffixed "postponed"? I notice that the proposal for 712 updated Table 15-3 so that cbEndOfSimTime now points to the "Pre-Postponed" region (should that also be "Pre-postponed"), but that cbReadOnlySynch still maps to the "Postponed" region. Is that intentional? Regards, Jim Vellenga --------------------------------------------------------- James H. Vellenga 978-262-6381 Engineering Director (FAX) 978-262-6636 Cadence Design Systems, Inc. vellenga@cadence.com 270 Billerica Rd Chelmsford, MA 01824-4179 "We all work with partial information." ---------------------------------------------------------- ] -----Original Message----- ] From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On ] Behalf Of Charlie Dawson ] Sent: Tuesday, May 17, 2005 9:56 PM ] To: Neil.Korpusik@sun.com ] Cc: SV-CC ] Subject: [sv-cc] [Fwd: P1800 instructions for editor - mantis ] 734, 709, 711 and 712] ] ] The SV-CC will meet tomorrow and look at this set of changes. ] ] -Chas ] ] ] -------- Original Message -------- ] Subject: P1800 instructions for editor - mantis 734, 709, 711 and 712 ] Date: Tue, 17 May 2005 18:51:09 -0700 ] From: Neil Korpusik <Neil.Korpusik@sun.com> ] Reply-To: Neil.Korpusik@sun.com ] To: chas ] CC: Mehdi Mohtashemi <Mehdi.Mohtashemi@synopsys.com>, ] Arturo Salz <Arturo.Salz@synopsys.com>, Stuart ] Sutherland <Stuart.Sutherland@sun.com>, Karen Pieper ] <Karen.Pieper@synopsys.com> ] References: <42850689.4010702@Sun.COM> <428508FE.10602@cadence.com> ] ] Hi Chas, ] ] Arturo pointed out that Mantis item 712 also touches the same ] text of the ] LRM. I have merged the text portion of that mantis item into ] this same file. ] For mantis item 712 I made the same 2 wording changes in ] order to make it ] consistent with the other paragraphs. ] ] "is specifically for" ---> "provides" ] "for user code" ---> "PLI application routines" ] ] ] Each of these text substitutions has been approved for a subset of the ] paragraphs by one of the committees. ] ] The svec approved the following in mantis items 709 and 711 ] (but not 712 nor 734). ] ] "is specifically for" ---> "provides" ] ] The svcc approved the following in mantis item 734 (but not in 712). ] ] "for user code" ---> "PLI application routines" ] ] It would probably be good if the svcc voted on these ] additional changes to ] ensure that all of them were approved by one of the committees. ] ] Note that there are a couple of other changes mentioned in ] mantis item 712 ] that are not shown in the attached document. They modify ] table 15-3 and ] figure 15-1. The modification to table 15-3 supercedes svcc ] mantis item 372. ] ] ] Neil ] ] ] ] Charles Dawson wrote: ] > Hi Neil et All, ] > ] > I took a look at these changes, and they seem okay to me. ] I will bring it ] > up at our next SV-CC meeting (Wednesday) anyway. I do ] want to point out that ] > Mantis Item 372 also deals with this section. ] > ] > -Chas ] > ] > ] > Neil Korpusik wrote: ] > ] >>Hi Chas, Mehdi, Arturo, Karen and Stu, ] >> ] >>Both the svec and the svcc have approved mantis items that ] touch the same ] >>paragraphs of the P1800 LRM. ] >> ] >> svec - mantis 709 and 711 ] >> svcc - mantis 734 ] >> ] >>Since mantis item 734 is the one with the highest number, ] Stu would typically ] >>apply this set of changes last. If he uses this algorithm ] some of the changes ] >>contained in mantis 709 and 711 will be lost. ] >> ] >>Attached is a pdf file that contains the text that should ] result after ] >>merging all three of these mantis items. ] >> ] >>After merging the text for these I noticed there there ] were a few places where ] >>wordsmithing done in one paragraph was not made to the ] same phrase in another. ] >>I took the liberty of making all of these consistent. ] There were only two ] >>phrases affected by this change: ] >> ] >> "is specifically for" --> "provides" ] >> "allows for" --> "allows" ] >> ] >>Other than those minor changes this should be an exact ] merge of the three ] >>mantis items. ] >> ] >>I am expecting that we will all be in agreement on this ] and that it won't be ] >>necessary to hold a joint conference call with the svec ] and svcc to approve ] >>this. ] >> ] >>Let me know what you think. This merged pdf may need to be ] added to one of ] >>the existing mantis items (734?). ] >> ] >>Neil ] >> ] >> ] >>BTW - I will be on vacation for the rest of the day and ] won't see any email ] >>until Monday. ] >> ] >> ] > ] > ] > ] ] -- ] --------------------------------------------------------------------- ] Neil Korpusik Tel: 408-720-4852 ] Staff Engineer Fax: 408-720-4850 ] Frontend Technologies - ASICs & Processors (FTAP) ] Sun Microsystems ] email: neil.korpusik@sun.com ] --------------------------------------------------------------------- ] ] ] ] -- ] Charles Dawson ] Senior Engineering Manager ] NC-Verilog Team ] Cadence Design Systems, Inc. ] 270 Billerica Road ] Chelmsford, MA 01824 ] (978) 262 - 6273 ] chas@cadence.com ] ] ]Received on Wed May 18 12:09:17 2005
This archive was generated by hypermail 2.1.8 : Wed May 18 2005 - 12:09:21 PDT