public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56444] mn10300.c:3228:16: error: unused variable ‘loops’ Date: Tue, 26 Feb 2013 10:49:00 -0000 [thread overview] Message-ID: <bug-56444-4-ozZF74W3An@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56444-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56444 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-26 10:49:30 UTC --- Author: rguenth Date: Tue Feb 26 10:49:25 2013 New Revision: 196280 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196280 Log: 2013-02-26 Richard Biener <rguenther@suse.de> PR target/56444 * config/mn10300/mn10300.c (mn10300_scan_for_setlb_lcc): Remove unused variable loops. Modified: trunk/gcc/ChangeLog trunk/gcc/config/mn10300/mn10300.c
next prev parent reply other threads:[~2013-02-26 10:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-25 14:57 [Bug target/56444] New: " amylaar at gcc dot gnu.org 2013-02-25 16:29 ` [Bug target/56444] " law at redhat dot com 2013-02-25 17:59 ` amylaar at gcc dot gnu.org 2013-02-25 18:40 ` law at redhat dot com 2013-02-26 10:49 ` rguenth at gcc dot gnu.org [this message] 2013-02-26 10:50 ` rguenth 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-56444-4-ozZF74W3An@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).