public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "orion at cora dot nwra.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61294] New: [4.9 Regression] erroneous memset used with constant zero length parameter warning
Date: Fri, 23 May 2014 15:29:00 -0000 [thread overview]
Message-ID: <bug-61294-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61294
Bug ID: 61294
Summary: [4.9 Regression] erroneous memset used with constant
zero length parameter warning
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: orion at cora dot nwra.com
Created attachment 32846
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32846&action=edit
preprocessed test case
$ g++ -std=c++11 -O2 -c test.cxx
In function 'void* memset(void*, int, size_t)',
inlined from 'static void
vtkDistributedDataFilter::AddConstantUnsignedCharPointArray(vtkUnstructuredGrid*,
const char*, unsigned char)' at test.cxx:31883:29:
test.cxx:15303:32: warning: call to '__warn_memset_zero_len' declared with
attribute warning: memset used with constant zero length parameter; this could
be due to transposed parameters
__warn_memset_zero_len ();
^
# g++ -v
Using built-in specs.
COLLECT_GCC=/usr/bin/g++
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.9.0/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --enable-multilib --with-system-zlib
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object
--enable-linker-build-id --with-linker-hash-style=gnu
--enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --enable-plugin
--enable-initfini-array --disable-libgcj
--with-isl=/builddir/build/BUILD/gcc-4.9.0-20140518/obj-x86_64-redhat-linux/isl-install
--with-cloog=/builddir/build/BUILD/gcc-4.9.0-20140518/obj-x86_64-redhat-linux/cloog-install
--enable-gnu-indirect-function --with-tune=generic --with-arch_32=i686
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.9.0 20140518 (Red Hat 4.9.0-5) (GCC)
No warning with 4.8.2 (or without -O2)
next reply other threads:[~2014-05-23 15:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 15:29 orion at cora dot nwra.com [this message]
2014-05-26 12:42 ` [Bug c++/61294] " rguenth at gcc dot gnu.org
2014-05-26 12:45 ` rguenth at gcc dot gnu.org
2014-05-26 12:45 ` rguenth at gcc dot gnu.org
2014-05-29 15:46 ` orion at cora dot nwra.com
2014-06-03 13:11 ` [Bug middle-end/61294] " jason at gcc dot gnu.org
2014-06-25 11:37 ` jakub at gcc dot gnu.org
2014-07-14 7:37 ` jakub at gcc dot gnu.org
2014-07-16 13:29 ` jakub at gcc dot gnu.org
2014-08-06 15:30 ` pinskia at gcc dot gnu.org
2014-10-30 10:40 ` jakub at gcc dot gnu.org
2014-11-24 16:45 ` rguenth at gcc dot gnu.org
2014-11-24 16:50 ` jakub at gcc dot gnu.org
2014-11-24 19:27 ` carlos at gcc dot gnu.org
2014-11-27 5:47 ` siddhesh at redhat dot com
2015-06-26 20:06 ` jakub at gcc dot gnu.org
2015-06-26 20:35 ` jakub at gcc dot gnu.org
2023-03-31 11:42 ` pinskia 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-61294-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: 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).