public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/47137] [4.6 Regression] gcc incorrectly combines assembly inputs Date: Mon, 03 Jan 2011 13:54:00 -0000 [thread overview] Message-ID: <bug-47137-4-ZwxtlTQywn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47137-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47137 --- Comment #9 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-01-03 13:54:28 UTC --- Does reverting the r168407 commit and instead applying Jie's first patch from http://gcc.gnu.org/ml/gcc/2010-12/msg00517.html fix all the present problems? If so, then please do that. It seems a lot safer at the present stage than more complicated fixes involving the Go driver.
next prev parent reply other threads:[~2011-01-03 13:54 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-31 20:20 [Bug driver/47137] New: " hjl.tools at gmail dot com 2010-12-31 20:24 ` [Bug driver/47137] " hjl.tools at gmail dot com 2010-12-31 20:26 ` hjl.tools at gmail dot com 2011-01-02 17:54 ` hjl at gcc dot gnu.org 2011-01-02 17:55 ` hjl.tools at gmail dot com 2011-01-02 22:07 ` hjl.tools at gmail dot com 2011-01-02 22:43 ` rguenth at gcc dot gnu.org 2011-01-03 12:31 ` jakub at gcc dot gnu.org 2011-01-03 13:24 ` hjl.tools at gmail dot com 2011-01-03 13:54 ` joseph at codesourcery dot com [this message] 2011-01-03 15:03 ` hjl at gcc dot gnu.org 2011-01-03 21:42 ` rguenth at gcc dot gnu.org 2011-01-03 23:31 ` ian at airs dot com 2011-01-03 23:33 ` ian at airs dot com 2011-01-04 10:22 ` jiez at gcc dot gnu.org 2011-01-04 10:30 ` jakub 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=bug-47137-4-ZwxtlTQywn@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).