public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pavel.morozkin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106797] Improvement: diagnose undefined behavior: not all declarations that refer to the same object or function have compatible type
Date: Wed, 31 Aug 2022 19:28:17 +0000	[thread overview]
Message-ID: <bug-106797-4-LG4y59IsUc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106797-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Pavel M <pavel.morozkin at gmail dot com> ---
Observation: if "static" is removed, then GCC generates:
<source>: In function 'f2':
<source>:10:18: error: conflicting types for 'x'; have 'int (*)[5]'
   10 |     extern int (*x)[5];
      |                  ^
<source>:5:18: note: previous declaration of 'x' with type 'int (*)[3]'
    5 |     extern int (*x)[3];
      |

      parent reply	other threads:[~2022-08-31 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 19:20 [Bug c/106797] New: " pavel.morozkin at gmail dot com
2022-08-31 19:24 ` [Bug c/106797] " jsm28 at gcc dot gnu.org
2022-08-31 19:28 ` pavel.morozkin at gmail dot com [this message]

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-106797-4-LG4y59IsUc@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).