public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/46967] lots of testsuite failures with libgomp on hppa-hp-hpux11.31
Date: Sun, 01 May 2011 22:09:00 -0000	[thread overview]
Message-ID: <bug-46967-4-irmbqiylcU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46967-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46967

--- Comment #5 from Hin-Tak Leung <htl10 at users dot sourceforge.net> 2011-05-01 22:02:03 UTC ---
(In reply to comment #4)
> Regarding comment #3, look at the libgomp test log file to see why the
> tests are failing on alphaev68-dec-osf5.1a.  I'm certain the problem
> is different from the hppa2.0w-hp-hpux11.31 issue, so a new PR
> should be opened.

Will do. am checking bug 40894 for 4.4.6 at the moment. When I finish updating
the status of that I'll send the test result to test-results, and file  a new
bug.


  parent reply	other threads:[~2011-05-01 22:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 19:12 [Bug libgomp/46967] New: " bugzilla-gcc at thewrittenword dot com
2011-01-27 20:17 ` [Bug libgomp/46967] " bugzilla-gcc at thewrittenword dot com
2011-01-27 20:49 ` dave at hiauly1 dot hia.nrc.ca
2011-05-01 19:03 ` htl10 at users dot sourceforge.net
2011-05-01 21:38 ` danglin at gcc dot gnu.org
2011-05-01 22:09 ` htl10 at users dot sourceforge.net [this message]
2011-05-01 22:26 ` htl10 at users dot sourceforge.net
2011-08-20  5:45 ` bugzilla-gcc at thewrittenword dot com
2011-08-20 17:04 ` dave.anglin at bell dot net
2014-11-25  2:40 ` danglin 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-46967-4-irmbqiylcU@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).