[Bug 1000707] New: Multiple is_substr() goals for one CDL item

[Bug 1000707] New: Multiple is_substr() goals for one CDL item

[bugzilla-daemon]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000707

           Summary: Multiple is_substr() goals for one CDL item
           Product: eCos
           Version: 3.0beta1
          Platform: Other (please specify)
        OS/Version: HostOS: All
            Status: ASSIGNED
          Severity: normal
          Priority: normal
         Component: ConfigTool
        AssignedTo: john@dallaway.org.uk
        ReportedBy: john@dallaway.org.uk
         QAContact: ecos-bugs@ecos.sourceware.org
             Class: ---


The ConfigTool "Resolve Conflicts" dialog does not cooperate well with the CDL
inference engine in the case of multiple is_substr() goals for a single CDL
item with an existing user_value. For example, the two goals:

   requires CYGOPT_USE1 implies is_substr(CYGOPT_EXAMPLE, "substring1")
   requires CYGOPT_USE2 implies is_substr(CYGOPT_EXAMPLE, "substring2")

will result in multiple CDL solutions which do not fully resolve the conflict
if CYGOPT_USE1 and CYGOPT_USE2 are enabled at the same time.

This issue is evident when enabling CYGHWR_THUMB for ARM architecture targets.
I will workaround by merging multiple is_substr() expressions into a single
goal for the time being.


-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

[Bug 1000707] Multiple is_substr() goals for one CDL item

[bugzilla-daemon]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000707


John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |Blocking_3.0-




-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.