public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8
Date: Thu, 23 Apr 2009 06:04:00 -0000	[thread overview]
Message-ID: <20090423060350.26695.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39852-17612@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from jakub at gcc dot gnu dot org  2009-04-23 06:03 -------
GCC 4.4.0 compiled glibc 2.10 works just fine for me on x86_64, i586, i686,
powerpc and powerpc64.

Anyway, if you say GCC 4.3.3 compiled glibc 2.8 works and 4.4.0 compiled
doesn't, then please do a binary search between 4.3.3 and 4.4.0 compiled
objects to find out on which CU it matters (say configure glibc with CC=gcc
CXX=g++,
then point PATH env var. to wher eyou have gcc 4.4.0 unpacked, build glibc,
verify your testcase breaks, then in the build tree
for i in [a-l]*/*.os; do mv ${i}{,.4.4}; done
change PATH to point to 4.3.3 gcc, make, see whether your testcase breaks or
not and depending on that continue with either half of the [a-l]* or [m-z]*
objects, etc.


-- 


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


  parent reply	other threads:[~2009-04-23  6:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 15:31 [Bug c/39852] New: " sega01 at go-beyond dot org
2009-04-23  0:09 ` [Bug middle-end/39852] " pinskia at gcc dot gnu dot org
2009-04-23  0:55 ` sega01 at go-beyond dot org
2009-04-23  0:57 ` pinskia at gcc dot gnu dot org
2009-04-23  1:10 ` sega01 at go-beyond dot org
2009-04-23  6:04 ` jakub at gcc dot gnu dot org [this message]
2009-04-23 20:59 ` sega01 at go-beyond dot org
2010-02-01  8:50 ` thunderwolf66102 at yahoo dot com
2010-02-01 11:14 ` mikpe at it dot uu dot se
     [not found] <bug-39852-4@http.gcc.gnu.org/bugzilla/>
2011-12-21 23:48 ` 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=20090423060350.26695.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).