public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/46434] New: crx-elf --enable-werror-always build fails Date: Thu, 11 Nov 2010 13:15:00 -0000 [thread overview] Message-ID: <bug-46434-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46434 Summary: crx-elf --enable-werror-always build fails Product: gcc Version: 4.6.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: amylaar@gcc.gnu.org Blocks: 44756 Target: crx-elf ../../../gcc/gcc/config/crx/crx.c: In function ‘crx_addr_reg_p’: ../../../gcc/gcc/config/crx/crx.c:595:7: error: variable ‘reg’ set but not used [-Werror=unused-but-set-variable] ../../../gcc/gcc/config/crx/crx.c: In function ‘crx_expand_epilogue’: ../../../gcc/gcc/config/crx/crx.c:1442:7: error: variable ‘return_reg’ set but n
next reply other threads:[~2010-11-11 13:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-11 13:15 amylaar at gcc dot gnu.org [this message] 2010-11-15 14:24 ` [Bug target/46434] " amylaar at gcc dot gnu.org 2010-11-19 19:26 ` amylaar at gcc dot gnu.org 2010-11-22 21:33 ` rth at gcc dot gnu.org 2010-11-22 22:06 ` amylaar 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-46434-4@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).