From: Jack Howarth <howarth@bromo.med.uc.edu>
To: java@gcc.gnu.org
Subject: shouldfail'ing sourcelocation
Date: Sat, 19 Jan 2013 15:27:00 -0000 [thread overview]
Message-ID: <20130119152716.GA4052@bromo.med.uc.edu> (raw)
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
next reply other threads:[~2013-01-19 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 15:27 Jack Howarth [this message]
2013-01-20 1:16 ` Bryce McKinlay
2013-02-02 12:57 Dominique Dhumieres
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130119152716.GA4052@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=java@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).