public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/19786] [4.0 Regression] Aliasing optimisation bug Date: Wed, 16 Feb 2005 20:04:00 -0000 [thread overview] Message-ID: <20050216165856.22495.qmail@sourceware.org> (raw) In-Reply-To: <20050206101741.19786.sylvain.pion@sophia.inria.fr> ------- Additional Comments From jakub at gcc dot gnu dot org 2005-02-16 16:58 ------- Actually, I do see problems in the tree dumps already. Particularly the trees look ok before LIM and are broken afterwards. loopinit->lim pseudo diff: <L97>:; D.16409_250 = &this_125->D.11755._M_impl._M_start; __i_251 = D.16409_250; D.16417_252 = *__i_251; *D.16417_252 = 1; this_109 = this_125; D.16452_108 = this_109->D.11755._M_impl._M_finish; SR.568_107 = D.16452_108; D.16460_97 = this_109->D.11755._M_impl._M_start; SR.571_93 = D.16460_97; if (SR.571_93 == SR.568_107) goto <L142>; else goto <L143>; <L143>:; -<L110>:; D.16491_352 = &this_125->D.11755._M_impl._M_finish; __i_353 = D.16491_352; SR.574_354 = *__i_353; D.16499_365 = SR.574_354 - 4B; D.16061_377 = *D.16499_365; +<L110>:; if (D.16061_377 != 0) goto <L144>; else goto <L117>; <L144>:; goto <bb 27> (<L136>); <L117>:; D.16432_339 = this_125->D.11755._M_impl._M_finish; D.16433_340 = D.16432_339 - 4B; this_125->D.11755._M_impl._M_finish = D.16433_340; this_599 = this_125; D.16452_598 = this_599->D.11755._M_impl._M_finish; SR.568_596 = D.16452_598; D.16460_588 = this_599->D.11755._M_impl._M_start; SR.571_587 = D.16460_588; if (SR.571_587 == SR.568_596) goto <L145>; else goto <L146>; <L146>:; goto <bb 20> (<L110>); <L145>:; goto <bb 27> (<L136>); ... <L142>:; <L136>:; return <retval>; *(*&this->D.11755._M_impl._M_finish - 4B) is hoisted before the loop as invariant, although it is not (each iteration of the loop decreases this->D.11755._M_impl._M_finish by 4 bytes). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19786
next prev parent reply other threads:[~2005-02-16 16:59 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-06 10:17 [Bug tree-optimization/19786] New: " sylvain.pion@sophia.inria.fr 2005-02-06 10:20 ` [Bug tree-optimization/19786] " sylvain.pion@sophia.inria.fr 2005-02-06 15:19 ` pinskia@gcc.gnu.org 2005-02-06 15:29 ` [Bug rtl-optimization/19786] [4.0 Regression] " pinskia@gcc.gnu.org 2005-02-07 3:24 ` pinskia at gcc dot gnu dot org 2005-02-07 3:25 ` pinskia at gcc dot gnu dot org 2005-02-07 3:39 ` pinskia at gcc dot gnu dot org 2005-02-07 3:42 ` pinskia at gcc dot gnu dot org 2005-02-16 19:46 ` jakub at gcc dot gnu dot org 2005-02-16 20:04 ` jakub at gcc dot gnu dot org [this message] 2005-02-16 22:00 ` [Bug tree-optimization/19786] " pinskia at gcc dot gnu dot org 2005-02-16 23:17 ` jakub at gcc dot gnu dot org 2005-02-17 3:30 ` jakub at gcc dot gnu dot org 2005-02-18 22:00 ` aoliva at gcc dot gnu dot org 2005-02-19 1:14 ` sylvain dot pion at sophia dot inria dot fr 2005-02-19 11:53 ` aoliva at gcc dot gnu dot org 2005-02-21 21:47 ` pinskia at gcc dot gnu dot org 2005-02-21 23:19 ` aoliva at redhat dot com 2005-02-21 23:23 ` dnovillo at redhat dot com 2005-02-22 11:32 ` cvs-commit at gcc dot gnu dot org 2005-02-22 12:02 ` pinskia at gcc dot gnu dot 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=20050216165856.22495.qmail@sourceware.org \ --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).