public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Martin Sebor <msebor@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] avoid incomplete types in -Warray-bounds (PR 86741)
Date: Tue, 31 Jul 2018 09:50:00 -0000	[thread overview]
Message-ID: <CAFiYyc1hOYPCgjBwx+SXW3VzOddVDNhJ4tB1Vx8rZszF+BCT+Q@mail.gmail.com> (raw)
In-Reply-To: <ab8dde91-4339-639d-15ee-97143bc0087c@gmail.com>

On Mon, Jul 30, 2018 at 10:16 PM Martin Sebor <msebor@gmail.com> wrote:
>
> The enhanced handling of MEM_REFs in -Warray-bounds assumes
> the object from whose address an offset is being computed has
> a complete type.  Since the size of such objects isn't known,
> whether the offset (or index) from its beginning is valid
> cannot be reliably determined.  The attached patch avoids
> dealing with such objects.

Looks ok to deal with the testcase, thus please install.

Richard.




> Martin

      reply	other threads:[~2018-07-31  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 20:16 Martin Sebor
2018-07-31  9:50 ` Richard Biener [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=CAFiYyc1hOYPCgjBwx+SXW3VzOddVDNhJ4tB1Vx8rZszF+BCT+Q@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=msebor@gmail.com \
    /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).