public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/13325] New: [tree-ssa] Weird warning on memcpy(d, s, 0)
Date: Fri, 05 Dec 2003 22:29:00 -0000	[thread overview]
Message-ID: <20031205222859.13325.falk@debian.org> (raw)

gcc (GCC) 3.5-tree-ssa 20031205 (merged 20031130) on alphaev68-unknown-linux-gnu

falk@juist:/tmp% cat test.c
void *memcpy(void *dest, const void *src, __SIZE_TYPE__ n);
void f (void *dest, const void *src) {
    memcpy (dest, src, 0);
}

falk@juist:/tmp% gcc -c -W test.c 
test.c: In function `f':

test.c:3: warning: statement with no effect

Well yeah, it has no effect, but things like these are often created by macros.
It seems unlikely that it marks a real mistake. Similar for memcmp etc.

-- 
           Summary: [tree-ssa] Weird warning on memcpy(d, s, 0)
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: minor
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: falk at debian dot org
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2003-12-05 22:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 22:29 falk at debian dot org [this message]
2003-12-05 22:53 ` [Bug c/13325] " pinskia at gcc dot gnu dot org
2003-12-05 23:48 ` [Bug middle-end/13325] " pinskia at gcc dot gnu dot org
2004-02-03  6:03 ` rth at gcc dot gnu dot org
2004-02-04  2:24 ` cvs-commit at gcc dot gnu dot org
2004-02-04  2:31 ` rth 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=20031205222859.13325.falk@debian.org \
    --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).