public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/23657] [4.1 Regression] Wrong code generated: too much optimized out Date: Wed, 31 Aug 2005 16:23:00 -0000 [thread overview] Message-ID: <20050831161942.12176.qmail@sourceware.org> (raw) In-Reply-To: <20050831160521.23657.qrczak@knm.org.pl> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-31 16:19 ------- Confirmed, between t41.copyrename2 and t42.dom2, the V_MAY_DEF is removed. After *next_8 = 7; Before: # TMT.51_18 = V_MAY_DEF <TMT.51_4>; *dest_2 = 7; I think we are forgetting to copy the alias info. I think this is fixed by the patch for PR 23509: http://gcc.gnu.org/ml/gcc-patches/2005-08/msg01647.html The tree-cfg.c part that is. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |pinskia at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Component|c |tree-optimization Ever Confirmed| |1 GCC build triplet|i686-pc-linux-gnu | GCC host triplet|i686-pc-linux-gnu | GCC target triplet|i686-pc-linux-gnu | Keywords| |alias, wrong-code Last reconfirmed|0000-00-00 00:00:00 |2005-08-31 16:19:38 date| | Summary|Wrong code generated: too |[4.1 Regression] Wrong code |much optimized out |generated: too much | |optimized out Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23657
next prev parent reply other threads:[~2005-08-31 16:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-31 16:05 [Bug c/23657] New: " qrczak at knm dot org dot pl 2005-08-31 16:23 ` pinskia at gcc dot gnu dot org [this message] 2005-08-31 22:14 ` [Bug tree-optimization/23657] [4.1 Regression] " qrczak at knm dot org dot pl 2005-08-31 22:23 ` pinskia at gcc dot gnu dot org 2005-08-31 22:23 ` qrczak at knm dot org dot pl
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=20050831161942.12176.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).