public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/63989] tree-ssa-strlen.c doesn't handle constant pointer plus and array refs if constant offset is smaller than known constant string length Date: Thu, 08 Jan 2015 21:31:00 -0000 [thread overview] Message-ID: <bug-63989-4-9CWBtBDFwM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63989-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63989 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Thu Jan 8 21:30:56 2015 New Revision: 219362 URL: https://gcc.gnu.org/viewcvs?rev=219362&root=gcc&view=rev Log: PR tree-optimization/63989 * params.def (PARAM_MAX_TRACKED_STRLENS): Increment default from 1000 to 10000. * tree-ssa-strlen.c (get_strinfo): Moved earlier. (get_stridx): If we don't have a record for certain SSA_NAME, but it is POINTER_PLUS_EXPR of some SSA_NAME we do with constant offset, call get_stridx_plus_constant. (get_stridx_plus_constant): New function. (zero_length_string): Don't use get_stridx here. * gcc.dg/strlenopt-27.c: New test. Added: trunk/gcc/testsuite/gcc.dg/strlenopt-27.c Modified: trunk/gcc/ChangeLog trunk/gcc/params.def trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa-strlen.c
next prev parent reply other threads:[~2015-01-08 21:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-20 9:31 [Bug tree-optimization/63989] New: " jakub at gcc dot gnu.org 2014-11-20 9:44 ` [Bug tree-optimization/63989] " jakub at gcc dot gnu.org 2014-11-20 11:20 ` rguenther at suse dot de 2014-11-21 9:38 ` jakub at gcc dot gnu.org 2014-12-08 17:25 ` jakub at gcc dot gnu.org 2015-01-08 21:31 ` jakub at gcc dot gnu.org [this message] 2015-04-22 12:01 ` jakub at gcc dot gnu.org 2015-07-16 9:18 ` rguenth at gcc dot gnu.org 2022-01-09 0:45 ` pinskia 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-63989-4-9CWBtBDFwM@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: linkBe 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).