public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rimvydas.jas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/101919] New: Inconsistent -Wstringop-overread warning with -flto
Date: Sun, 15 Aug 2021 08:43:50 +0000 [thread overview]
Message-ID: <bug-101919-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101919
Bug ID: 101919
Summary: Inconsistent -Wstringop-overread warning with -flto
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: rimvydas.jas at gmail dot com
Target Milestone: ---
$ cat gl_test.f90
program foo
implicit none
character(len=100) :: c =' '
if (c(1:12) == 'Accumulated ') c = c(13:len_trim(c))
end program
$ gfortran -Wall -Wextra gl_test.f90
$ gfortran -Wall -Wextra -flto gl_test.f90
gl_test.f90: In function 'foo':
gl_test.f90:4:52: warning: '__builtin_memmove' reading 100 bytes from a region
of size 88 [-Wstringop-overread]
4 | if (c(1:12) == 'Accumulated ') c = c(13:len_trim(c))
| ^
gl_test.f90:3:23: note: at offset 12 into source object 'c' of size 100
3 | character(len=100) :: c =' '
| ^
next reply other threads:[~2021-08-15 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 8:43 rimvydas.jas at gmail dot com [this message]
2021-11-09 19:35 ` [Bug fortran/101919] " msebor at gcc dot gnu.org
2021-11-09 20:39 ` anlauf at gcc dot gnu.org
2021-11-09 21:50 ` aldot at gcc dot gnu.org
2021-11-10 20:25 ` anlauf at gcc dot gnu.org
2021-11-10 20:55 ` anlauf at gcc dot gnu.org
2023-07-27 6:30 ` rimvydas.jas 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-101919-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).