public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/104088] [12/13 Regression] '-O2' (or higher) GCN offloading (only) 'libgomp.oacc-c-c++-common/vprop.c' excess errors: 'warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]'
Date: Mon, 21 Nov 2022 13:18:46 +0000	[thread overview]
Message-ID: <bug-104088-4-fgulRvrzNk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104088-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
I did have a look at this the other day. If I recall correctly, the issue was
that

  tree destsize = compute_objsize (dest, stmt, ostype, &aref, &ptr_qry);

in strlen_pass::maybe_warn_overflow (in file tree-ssa-strlen.cc) wrongly
returned 0
for a   var[i]._char_memb. Somewhere ('var'?) was a variable which did not use
the 64bit generic memory space but a 32-byte one. My feeling is that the
problem is related to having a non-generic memory space.

(Disclaimer: It was a couple of days back when I had a quick look and I might
misremember. The 'var[i]._char_memb' matches pattern wise but the name was
surely different.)

However, reading now the commit message title, quoted in comment 0 - "Use
enclosing object size if it's smaller than member" -, explains why the 1-byte
character type's length is not used even if it looks fine.

  parent reply	other threads:[~2022-11-21 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 10:24 [Bug middle-end/104088] New: [12 " tschwinge at gcc dot gnu.org
2022-01-18 11:12 ` [Bug middle-end/104088] " rguenth at gcc dot gnu.org
2022-03-21 15:54 ` tschwinge at gcc dot gnu.org
2022-05-06  8:32 ` [Bug middle-end/104088] [12/13 " jakub at gcc dot gnu.org
2022-10-19  9:48 ` rguenth at gcc dot gnu.org
2022-11-21 13:18 ` burnus at gcc dot gnu.org [this message]
2023-05-08 12:23 ` [Bug middle-end/104088] [12/13/14 " rguenth at gcc dot gnu.org
2024-03-22 14:06 ` law 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-104088-4-fgulRvrzNk@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).