10 research outputs found

    Immigrant Health Report: Barriers to Health Care for Immigrant and Refugee Populations

    No full text
    The REACH Healthcare Foundation is beginning implementation of a new five-year strategic plan that includes attention to highly vulnerable populations, including legal and undocumented immigrants and refugee populations. This report identifies immigrants' barriers to access health care and coverage, as well as findings and recommendations from a series of community conversations with key leaders of organizations working to support immigrant health and well-being in the Kansas City metropolitan area and with immigrant consumer groups

    Debugging and Testing Optimizers Through . . .

    No full text
    We present a novel technique called comparison checking that helps optimizer writers debug optimizers by testing, for given inputs, that the semantics of a program are not changed by the application of optimizations. We have successfully applied comparison checking to a large class of program transformations that alter (1) the relative ordering in which values are computed by the intermediate code statements, (2) the form of the intermediate code statements, and (3) the control flow structure using code replication. We outline the key steps that lead to the automation of comparison checking. The application of comparison checking to test the implementations of high level loop transformations, low level code optimizations, and global register allocation for given program inputs is then described

    Debugging of Optimized Code through Comparison Checking

    No full text
    We present a new approach to the debugging of optimized code through comparison checking. In this scheme, both the unoptimized and optimized versions of an application execute, and values they compute are compared in order to ensure that the behaviors of the two versions are the same. To determine what values should be compared and where the comparisons must take place, statement instances in the unoptimized code are mapped to statement instances in the optimized code. The mappings are derived automatically as optimizations are performed. Annotations for both versions of the code are developed from the mappings. Using the annotations, a driver checks, while the programs are executing, that both programs are producing the same values. If values are different, the user determines if there is a bug in the unoptimized code. If so, a conventional debugger is used to debug the code. If the bug is in the optimized code, the user is told where in the code the problem occurred and what optimiza..

    Comparison checking

    No full text
    corecore