public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gseanmcg at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/35531] Assembler failure while compiling libgcc Date: Tue, 07 Dec 2010 20:07:00 -0000 [thread overview] Message-ID: <bug-35531-4-ZWFU1ZyaES@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-35531-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35531 Sean McGovern <gseanmcg at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gseanmcg at gmail dot com --- Comment #13 from Sean McGovern <gseanmcg at gmail dot com> 2010-12-07 20:06:27 UTC --- Since I have had successful builds of both 4.5.x and 4.6.x of gcc using current GNU binutils (2.20.1.x) and Sun ld, can this bug be closed?
next parent reply other threads:[~2010-12-07 20:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-35531-4@http.gcc.gnu.org/bugzilla/> 2010-12-07 20:07 ` gseanmcg at gmail dot com [this message] 2010-12-09 1:41 ` bfriesen at simple dot dallas.tx.us 2008-03-10 21:18 [Bug bootstrap/35531] New: " bfriesen at simple dot dallas dot tx dot us 2008-03-10 21:23 ` [Bug bootstrap/35531] " pinskia at gcc dot gnu dot org 2008-03-10 21:50 ` bfriesen at simple dot dallas dot tx dot us 2008-03-10 23:06 ` bfriesen at simple dot dallas dot tx dot us 2008-03-10 23:21 ` pinskia at gcc dot gnu dot org 2008-03-11 11:17 ` ubizjak at gmail dot com 2008-03-11 15:51 ` bfriesen at simple dot dallas dot tx dot us 2008-03-11 15:54 ` pinskia at gcc dot gnu dot org 2008-03-11 16:20 ` ubizjak at gmail dot com 2008-03-11 16:36 ` bfriesen at simple dot dallas dot tx dot us 2008-07-19 21:33 ` pinskia at gcc dot gnu dot org 2009-07-01 11:58 ` marek dot rouchal at infineon dot com 2009-07-01 16:42 ` bfriesen at simple dot dallas dot tx dot us
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-35531-4-ZWFU1ZyaES@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: 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).