public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/55637] FAIL: sourcelocation output - source compiled test
Date: Fri, 07 Feb 2014 15:07:00 -0000 [thread overview]
Message-ID: <bug-55637-8172-j85RFQvXwc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55637-8172@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55637
--- Comment #13 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> What should we do about this test? Having it fail everywhere a current binutils
> version is used causes lots of noise in testsuite results.
Since nobody cared to fix the tests since more than one year, IMO the answer is
obvious: remove it.
next prev parent reply other threads:[~2014-02-07 15:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 3:47 [Bug libgcj/55637] New: " danglin at gcc dot gnu.org
2013-01-08 16:16 ` [Bug libgcj/55637] " ro at gcc dot gnu.org
2013-01-15 18:14 ` dominiq at lps dot ens.fr
2013-08-09 13:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-09-03 15:47 ` doko at gcc dot gnu.org
2013-09-03 15:50 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-09-04 10:33 ` mark at gcc dot gnu.org
2013-09-04 10:34 ` doko at gcc dot gnu.org
2013-09-04 10:38 ` mark at gcc dot gnu.org
2013-09-04 11:38 ` mark at gcc dot gnu.org
2013-09-04 11:44 ` mark at gcc dot gnu.org
2013-09-04 12:02 ` mark at gcc dot gnu.org
2014-02-07 15:01 ` ro at gcc dot gnu.org
2014-02-07 15:07 ` dominiq at lps dot ens.fr [this message]
2014-02-20 12:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-02-20 14:05 ` ro at gcc dot gnu.org
2014-04-01 10:19 ` dominiq at gcc dot gnu.org
2014-04-22 11:35 ` jakub at gcc dot gnu.org
2014-07-16 13:26 ` jakub at gcc dot gnu.org
2014-10-30 10:36 ` jakub at gcc dot gnu.org
2015-06-26 20:11 ` jakub at gcc dot gnu.org
2015-06-26 20:36 ` jakub at gcc dot gnu.org
2015-06-26 21:18 ` pinskia at gcc dot gnu.org
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=bug-55637-8172-j85RFQvXwc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).