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/41844] lto1: warning: unknown register name: line-length-none Date: Tue, 16 Aug 2011 10:20:00 -0000 [thread overview] Message-ID: <bug-41844-4-LjkoeXiX2r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41844-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41844 --- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-08-16 10:02:40 UTC --- I don't think there's any real change from what I said in <http://gcc.gnu.org/ml/gcc-patches/2010-07/msg02242.html>: the information may be in the .opt files (if an option is marked for a front end *and* is not marked as Common or Target, then it's front-end-specific) though the relevant parts of the driver may still be working with different structures; you could implement it, but you'd need to get the logical option information to the right part of the driver.
next prev parent reply other threads:[~2011-08-16 10:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41844-4@http.gcc.gnu.org/bugzilla/> 2011-08-16 8:25 ` rguenth at gcc dot gnu.org 2011-08-16 8:27 ` rguenth at gcc dot gnu.org 2011-08-16 10:20 ` joseph at codesourcery dot com [this message] 2011-10-25 14:26 ` rguenth at gcc dot gnu.org 2011-10-26 9:30 ` rguenth at gcc dot gnu.org 2011-10-26 9:32 ` rguenth at gcc dot gnu.org 2009-10-27 8:43 [Bug fortran/41844] New: " linuxl4 at sohu dot com 2009-10-27 10:27 ` [Bug driver/41844] " rguenth at gcc dot gnu dot org 2010-06-03 15:08 ` rguenth 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=bug-41844-4-LjkoeXiX2r@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).