public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/25567]  New: 4 * set but never used
Date: Mon, 26 Dec 2005 14:46:00 -0000	[thread overview]
Message-ID: <bug-25567-9596@http.gcc.gnu.org/bugzilla/> (raw)

I just tried to compile the gcc-4.2 snapshot 20051224 with the Intel C
compiler. It said

1.

../../src/gcc-4.2-20051224/gcc/c-decl.c(4486): remark #593: variable
"type_as_written" was set but
never used

The source code is

    tree type_as_written;

I have read the source code, and I agree with the compiler.
The local variable is only ever written to. Suggest delete local variable.

2.

../../src/gcc-4.2-20051224/gcc/tree-cfg.c(3083): remark #593: variable "src"
was set but never used

The source code is

  basic_block new_bb, after_bb, dest, src;

More of the same.

3.

../../src/gcc-4.2-20051224/gcc/tree-outof-ssa.c(1843): remark #593: variable
"changed" was set but
never used

The source code is

  bool changed;

More of the same.

4.

../../src/gcc-4.2-20051224/gcc/tree-ssa-copy.c(352): remark #593: variable
"lhs" was set but never
used

The source code is

  tree lhs, rhs;

More of the same.


-- 
           Summary: 4 * set but never used
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dcb314 at hotmail dot com
  GCC host triplet: x86_64-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25567


             reply	other threads:[~2005-12-26 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 14:46 dcb314 at hotmail dot com [this message]
2005-12-26 17:13 ` [Bug other/25567] " pinskia at gcc dot gnu dot org
2006-01-29 21:19 ` pinskia at gcc dot gnu dot org
2006-02-06 14:33 ` pinskia at gcc dot gnu dot org
2010-05-06 10:56 ` manu 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-25567-9596@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: link
Be 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).