public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/26175] [4.2 Regression] In gcc-4.2.0 libgomp/.../powerpc/futex.h SYS_futex undefined
Date: Tue, 06 Jun 2006 04:01:00 -0000	[thread overview]
Message-ID: <20060606035958.15747.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26175-11706@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from malitzke at metronets dot com  2006-06-06 03:59 -------
Good to see the GCC release manager looking at things from a user perspective,
and not just looking at an individual leaf in a forest.

Regarding the powerpc specific issues; I was able for just one day to compile a
complete glibc package. Now, after major work on mainline binutils (the one
with daily snapshots on ftp:gcc.gnu.org) It can not even pass a significant
portion of its own testsuite (while the ix86 build does fine). After having
been repeatedly told that the user community should not bother the
_illustrious_ glibc developers with build problems I have refrained from
contacting the binutils folks.

The steering committee, wisely, has recognized that the gcc group can __not__
contnuously and exhaustively test all software changes on the __vast__ array of
hardware configurations and thus has sought help from the user community. The
operating principle being that ""All bugs are shallow if there are thousands of
eyes looking "" (imperfect quote). 


-- 


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


  parent reply	other threads:[~2006-06-06  4:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 16:07 [Bug bootstrap/26175] New: " malitzke at metronets dot com
2006-02-08 16:43 ` [Bug bootstrap/26175] " rguenth at gcc dot gnu dot org
2006-02-08 16:50 ` [Bug libgomp/26175] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-02-10  6:36 ` pinskia at gcc dot gnu dot org
2006-05-21 20:21 ` pinskia at gcc dot gnu dot org
2006-05-22  8:31 ` jakub at gcc dot gnu dot org
2006-05-23  0:49 ` malitzke at metronets dot com
2006-06-03 22:11 ` pinskia at gcc dot gnu dot org
2006-06-04 17:35 ` mmitchel at gcc dot gnu dot org
2006-06-06  4:01 ` malitzke at metronets dot com [this message]
2006-06-20  9:56 ` jakub at gcc dot gnu dot org
2006-06-23  4:36 ` pinskia at gcc dot gnu dot 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=20060606035958.15747.qmail@sourceware.org \
    --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).