public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eb at emlix dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106503] New: "const char []" in local scope never initialized
Date: Tue, 02 Aug 2022 07:31:11 +0000	[thread overview]
Message-ID: <bug-106503-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106503

            Bug ID: 106503
           Summary: "const char []" in local scope never initialized
           Product: gcc
           Version: 11.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: eb at emlix dot com
  Target Milestone: ---

Given the following test program:

------------
#include <sys/uio.h>
#include <string.h>

#define WRITEL(str) \
                do { \
                        wdata[wpos].iov_base = (void*)(str); \
                        wdata[wpos].iov_len = strlen(str); \
                        wlen += wdata[wpos].iov_len; \
                        wpos++; \
                } while (0)

int main(int argc, char **argv)
{
        struct iovec wdata[20];
        unsigned int wpos = 0;
        ssize_t wlen = 0;
        int i = (argc > 1) ? 1 : 0;

        WRITEL("foo");
        if (argc) {
                const char junk[] = "abc";
                WRITEL(junk + i);
        } else {
                const char *junk = "def";
                WRITEL(junk + i);
        }
        WRITEL("baz\n");

        return writev(1, wdata, wpos) > 0 ? 0 : 1;
}
------------

For gcc 10 and before, and gcc 11, 12, or 13
(b06a282921c71bbc5cab69bc515804bd80f55e92) when used with -O0, this outputs:

$ ./Ch
fooabcbaz

>From gcc 11 on when using -O1 or more it does not seem to initialize the "junk"
buffer, so it may output random things:

$ ./Ch 
foocbaz
$ ./Ch 
foo�baz
$ ./Ch 
foo+baz
$ ./Ch 
foo baz
$ ./Ch 
foo[baz

I have seen the same behavior on both amd64 and sparc32, with distro compilers
(openSUSE, Gentoo) as well as an unpatched gcc13 built with Gentoo ebuilds.

             reply	other threads:[~2022-08-02  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  7:31 eb at emlix dot com [this message]
2022-08-02  7:36 ` [Bug c/106503] " eb at emlix dot com
2022-08-02  7:37 ` pinskia at gcc dot gnu.org
2022-08-02  7:47 ` pinskia at gcc dot gnu.org
2022-08-02  9:08 ` eb at emlix dot com
2022-08-02  9:44 ` redi at gcc dot gnu.org
2022-08-02 10:01 ` redi 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-106503-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).