public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/12644] New: Gcc 3.3.2 failed on glibc Date: Thu, 16 Oct 2003 17:48:00 -0000 [thread overview] Message-ID: <20031016174848.12644.hjl@lucon.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12644 Summary: Gcc 3.3.2 failed on glibc Product: gcc Version: 3.3.2 Status: UNCONFIRMED Severity: critical Priority: P1 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl at lucon dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: ia64-unknown-linux-gnu GCC host triplet: ia64-unknown-linux-gnu GCC target triplet: ia64-unknown-linux-gnu Gcc 3.3.2 failed to compile a working glibc due to a missing patch: http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00392.html As the result, glibc doesn't work correctly on ia64: http://sources.redhat.com/ml/libc-hacker/2003-10/msg00011.html
next reply other threads:[~2003-10-16 17:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-16 17:48 hjl at lucon dot org [this message] 2003-10-16 17:51 ` [Bug target/12644] " hjl at lucon dot org 2003-10-16 17:53 ` hjl at lucon dot org 2003-10-17 15:22 ` [Bug target/12644] [3.3 only] " pinskia at gcc dot gnu dot org 2003-10-23 0:32 ` wilson 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=20031016174848.12644.hjl@lucon.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: 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).