public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105316] New: Seemingly bogus -Wdangling-pointer from ppc/ppc64 kernel printk with gcc12
Date: Wed, 20 Apr 2022 03:24:49 +0000	[thread overview]
Message-ID: <bug-105316-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105316
           Summary: Seemingly bogus -Wdangling-pointer from ppc/ppc64
                    kernel printk with gcc12
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: raj.khem at gmail dot com
  Target Milestone: ---

I have reduced this case from ppc kernel 5.15, this breaks the kernel build as
the warning is treated as error. 

ftrace.i
======================

int _printk(const char *fmt, ...);

static void ftrace_modify_code() {
 _printk("replaced (%s)", ({ char __str[sizeof("00000000 00000000")]; __str;
}));
}


=====================

powerpc64le-yoe-linux-musl-gcc -c ftrace.i -Werror=dangling-pointer 
ftrace.i: In function 'ftrace_modify_code':
ftrace.i:4:2: error: using a dangling pointer to '__str'
[-Werror=dangling-pointer=]
    4 |  _printk("replaced (%s)", ({ char __str[sizeof("00000000 00000000")];
__str; }));
      | 
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ftrace.i:4:35: note: '__str' declared here
    4 |  _printk("replaced (%s)", ({ char __str[sizeof("00000000 00000000")];
__str; }));
      |                                   ^~~~~
cc1: some warnings being treated as errors

             reply	other threads:[~2022-04-20  3:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  3:24 raj.khem at gmail dot com [this message]
2022-04-20  3:29 ` [Bug middle-end/105316] " pinskia at gcc dot gnu.org
2022-04-20  3:35 ` raj.khem at gmail dot com

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-105316-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).