public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghazi@caip.rutgers.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/10974] Bootstrap failure Date: Sun, 01 Jun 2003 13:56:00 -0000 [thread overview] Message-ID: <20030601135640.15212.qmail@sources.redhat.com> (raw) In-Reply-To: <20030525155628.10974.bugzilla-gcc@thewrittenword.com> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10974 ------- Additional Comments From ghazi@caip.rutgers.edu 2003-06-01 13:56 ------- Subject: Re: Bootstrap failure > From: David Edelsohn <dje@watson.ibm.com> > > Kaveh, > Would you plesae consider updating the libiberty physical memory > check on AIX with this patch? > David Sure. Though I don't have any AIX boxes at all for testing it. Can I assume that you verified physmem is still correctly activated on AIX4.3.3 and AIX5? Thanks, --Kaveh -- Kaveh R. Ghazi ghazi@caip.rutgers.edu ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2003-06-01 13:56 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-25 16:05 [Bug bootstrap/10974] New: " bugzilla-gcc@thewrittenword.com 2003-05-25 16:16 ` [Bug bootstrap/10974] " bugzilla-gcc@thewrittenword.com 2003-05-26 17:51 ` dhazeghi@yahoo.com 2003-05-26 18:00 ` dhazeghi@yahoo.com 2003-05-26 18:09 ` pinskia@physics.uc.edu 2003-05-26 18:31 ` dje@watson.ibm.com 2003-06-01 13:56 ` ghazi@caip.rutgers.edu [this message] 2003-06-02 3:38 ` dje@watson.ibm.com 2003-06-02 11:48 ` ghazi@caip.rutgers.edu 2003-06-02 11:53 ` bugzilla-gcc@thewrittenword.com 2003-06-02 18:16 ` dje@watson.ibm.com 2003-06-08 3:43 ` dhazeghi@yahoo.com 2003-06-08 3:53 ` dje@watson.ibm.com 2003-06-08 5:27 ` ghazi@caip.rutgers.edu 2003-06-09 3:19 ` pinskia@physics.uc.edu 2003-06-09 5:20 ` cvs-commit@gcc.gnu.org 2003-06-09 5:41 ` ghazi@gcc.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=20030601135640.15212.qmail@sources.redhat.com \ --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: linkBe 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).