Ticket #4 (defect)

Opened 1 year ago

Last modified 1 year ago

barrier2_neg should not (necessarily) fail at compile time

Status: closed (fixed)

Reported by: gary Assigned to: apokayi
Priority: major Milestone:
Component: component1 Version:
Keywords: guts Cc:

When run against GCC/UPC version 4.0.3.4, this test issues the following diagnostics:

-------------->      Working on unit -- barrier2_neg\n

ERROR: The NEGATIVE unit [barrier2_neg] pass the compilation phase
The unit will not be run!!!
TEST FAILED for the unit [barrier2_neg]

Looking into this problem further, the body of the test case is:

        /*
         * To check that upc_notify and upc_wait statements should be
         * called in alternating sequence, starting with a upc_notify
         * and ending with a upc_wait statement
         * so the compiler must raise an ERROR here !!!
         */

        upc_notify 1; upc_notify 2; upc_notify 3;

        upc_wait 1; upc_wait 2; upc_wait 3;

Although this should fail at runtime, I don't think that spec. says this should be detected at compile time.

Change History

09/06/07 16:27:21: Modified by sbahra

  • owner changed from somebody to apokayi.

09/20/07 05:12:52: Modified by apokayi

  • status changed from new to closed.
  • resolution set to fixed.

drop the test case because it is too strict