public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/97175] [11 Regression] ICE in maybe_warn_for_bound, at builtins.c:3483 since r11-2928-gd14c547abd484d35
Date: Wed, 23 Sep 2020 21:11:00 +0000 [thread overview]
Message-ID: <bug-97175-4-MH6WvWxkRa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97175-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97175
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:6edc8f5bfe7d9db8fb8bd37bb8086a69850c6c6d
commit r11-3409-g6edc8f5bfe7d9db8fb8bd37bb8086a69850c6c6d
Author: Martin Sebor <msebor@redhat.com>
Date: Wed Sep 23 15:04:32 2020 -0600
Handle DECLs and EXPRESSIONs consistently (PR middle-end/97175).
gcc/ChangeLog:
PR middle-end/97175
* builtins.c (maybe_warn_for_bound): Handle both DECLs and
EXPRESSIONs
in pad->dst.ref, same is pad->src.ref.
gcc/testsuite/ChangeLog:
PR middle-end/97175
* gcc.dg/Wstringop-overflow-44.c: New test.
next prev parent reply other threads:[~2020-09-23 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 9:13 [Bug c/97175] New: ice in maybe_warn_for_bound, at builtins.c:3483 dcb314 at hotmail dot com
2020-09-23 10:22 ` [Bug tree-optimization/97175] [11 Regression] ICE in maybe_warn_for_bound, at builtins.c:3483 since r11-2928-gd14c547abd484d35 marxin at gcc dot gnu.org
2020-09-23 16:25 ` [Bug middle-end/97175] " msebor at gcc dot gnu.org
2020-09-23 21:11 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-23 21:43 ` msebor at gcc dot gnu.org
2020-09-23 21:46 ` msebor at gcc dot gnu.org
2020-09-24 7:02 ` dcb314 at hotmail dot com
2020-09-24 16:11 ` msebor at gcc dot gnu.org
2020-09-24 16:23 ` dcb314 at hotmail dot com
2020-09-24 20:52 ` msebor 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-97175-4-MH6WvWxkRa@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).