public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/39004] New: Revision 143730 breaks LTO Date: Wed, 28 Jan 2009 14:57:00 -0000 [thread overview] Message-ID: <bug-39004-682@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 684 bytes --] I got cc1: warnings being treated as errors ../../src-lto/gcc/lto-function-in.c: In function âinput_local_var_declâ: ../../src-lto/gcc/lto-function-in.c:1135: error: unused variable âcontext_tagâ ../../src-lto/gcc/lto-function-in.c:1134: error: unused variable âcontextâ make[5]: *** [lto-function-in.o] Error 1 -- Summary: Revision 143730 breaks LTO Product: gcc Version: lto Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: dnovillo at google dot com ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39004
next reply other threads:[~2009-01-28 14:57 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-28 14:57 hjl dot tools at gmail dot com [this message] 2009-01-28 15:05 ` [Bug middle-end/39004] " dnovillo at gcc dot gnu dot org 2009-01-28 15:17 ` dnovillo 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-39004-682@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).