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 tree-optimization/96665] [11 regression] new FAILs for gcc.dg/strlenopt-55.c after r11-2709
Date: Tue, 18 Aug 2020 18:59:33 +0000 [thread overview]
Message-ID: <bug-96665-4-nyQJSTTR8u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96665-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96665
--- Comment #3 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:d367f5fcb579d21c3093cf5c464f5787fe584a1d
commit r11-2743-gd367f5fcb579d21c3093cf5c464f5787fe584a1d
Author: Martin Sebor <msebor@redhat.com>
Date: Tue Aug 18 12:57:18 2020 -0600
PR middle-end/96665 - memcmp of a constant string not folded
Related:
PR middle-end/78257 - missing memcmp optimization with constant arrays
gcc/ChangeLog:
PR middle-end/96665
PR middle-end/78257
* expr.c (convert_to_bytes): Replace statically allocated buffer
with
a dynamically allocated one of sufficient size.
gcc/testsuite/ChangeLog:
PR middle-end/96665
PR middle-end/78257
* gcc.dg/memcmp-5.c: New test.
next prev parent reply other threads:[~2020-08-18 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 22:45 [Bug tree-optimization/96665] New: " seurer at gcc dot gnu.org
2020-08-18 7:19 ` [Bug tree-optimization/96665] " marxin at gcc dot gnu.org
2020-08-18 16:34 ` msebor at gcc dot gnu.org
2020-08-18 18:59 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-18 19:00 ` [Bug tree-optimization/96665] [11 regression] memcmp of a constant string not folded 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-96665-4-nyQJSTTR8u@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).