[sv-ec] RE: soft constraint proposal

From: Arturo Salz <Arturo.Salz@synopsys.com>
Date: Mon Sep 26 2011 - 09:29:20 PDT

The issue of ordering exists because of the definition of soft - since they can be overridden, we must define a priority.

The problem with an explicit ordering is that creating such an ordering would put all the burden on the users. It would make the syntax more complex (require the priority) and would make soft constraints even harder to use. Plus, we would also still need to determine an implicit ordering for all constraints with the same explicit priority. The current conceptual model of having constraints override "earlier" constraints seems to fit well with the existing expectation. Incidentally, I don't believe compilation order plays a role in the ordering.

                Arturo

From: Miller Hillel-R53776 [mailto:r53776@freescale.com]
Sent: Monday, September 26, 2011 6:01 AM
To: Arturo Salz; 'sv-ec@eda.org' (sv-ec@eda.org)
Subject: RE: soft constraint proposal

Arturo,

Is it a good idea to do implicit priority based on ordering of constructs?
This may have some pitfalls:

- Debugging tool complexity.

- Behavior changing based on compilation order.

- I don't recall precedence for this type of prioritization.

Perhaps an explicit ordering would be safer.

Thanks
Hillel

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Arturo Salz
Sent: Monday, September 26, 2011 1:19 AM
To: 'sv-ec@eda.org' (sv-ec@eda.org)
Subject: [sv-ec] soft constraint proposal

I have uploaded a new proposal for Mantis 2987. The new write-up incorporates all the feedback we've had, including the following:

- Makes soft a keyword.

- Uses the suggested "disable soft" instead of empty dist to reset soft constraints.

- Decouples the disable functionality from the soft-dist. Now the two features can be specified separately.

- Includes the BNF change from solve_before_primary to constraint_primary.

    Arturo

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon Sep 26 09:31:38 2011

This archive was generated by hypermail 2.1.8 : Mon Sep 26 2011 - 09:31:40 PDT