From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10410 invoked by alias); 19 Jan 2013 15:27:22 -0000 Received: (qmail 10402 invoked by uid 22791); 19 Jan 2013 15:27:21 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,TW_GC,TW_IB X-Spam-Check-By: sourceware.org Received: from bromo.med.uc.edu (HELO bromo.med.uc.edu) (129.137.3.146) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 19 Jan 2013 15:27:17 +0000 Received: from bromo.med.uc.edu (localhost.localdomain [127.0.0.1]) by bromo.med.uc.edu (Postfix) with ESMTP id D2AA1400007 for ; Sat, 19 Jan 2013 10:27:16 -0500 (EST) Received: (from howarth@localhost) by bromo.med.uc.edu (8.14.3/8.14.3/Submit) id r0JFRGtL004094 for java@gcc.gnu.org; Sat, 19 Jan 2013 10:27:16 -0500 Date: Sat, 19 Jan 2013 15:27:00 -0000 From: Jack Howarth To: java@gcc.gnu.org Subject: shouldfail'ing sourcelocation Message-ID: <20130119152716.GA4052@bromo.med.uc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg00006.txt.bz2 How exactly can we shouldfail the sourcelocation test on those platforms like darwin which don't support dwarf4... To make this test pass, one need to have up-to-date addr2line installed to parse the dwarf4 data format. I see the comments... # # Run the test specified by srcfile and resultfile. compile_args and # exec_args are options telling this proc how to work. # `no-link' don't try to link the program # `no-exec' don't try to run the test # `xfail-gcj' compilation from source will fail # `xfail-javac' compilation with javac will fail # `xfail-gcjC' compilation with gcj -C will fail # `shouldfail' compilation from source is supposed to fail # This is different from xfail, which marks a known # failure that we just haven't fixed. # A compilation marked this way should fail with any # front end. # `xfail-byte' compilation from bytecode will fail # `xfail-exec' exec will fail # `xfail-output' # output will be wrong # `xfail-byte-output' # output will be wrong when compiled from bytecode # `xfail-source-output' # output will be wrong when compiled from source code # `need-threads' # test relies on thread support # in libjava/testsuite/lib/libjava.exp but no evidence of these being used on any particular test for specified targets in the libjava testsuite. Thanks in advance for any advice here. Jack