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/29333] Jump threading getting in the way of PHI-OPT Date: Tue, 03 Oct 2006 16:11:00 -0000 [thread overview] Message-ID: <20061003161126.12146.qmail@sourceware.org> (raw) In-Reply-To: <bug-29333-13346@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2006-10-03 16:11 ------- Actually this is a case where jump threading gets in the way of PHI-OPT. Really PHI-OPT should be put before VRP and DOM, I don't know why it was not. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-10-03 16:11:22 date| | Summary|Generation of MAX_EXPRs and |Jump threading getting in |MIN_EXPRs missed by phiopt |the way of PHI-OPT http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29333
next prev parent reply other threads:[~2006-10-03 16:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-03 16:04 [Bug tree-optimization/29333] New: Generation of MAX_EXPRs and MIN_EXPRs missed by phiopt roberto dot costa at st dot com 2006-10-03 16:05 ` [Bug tree-optimization/29333] " roberto dot costa at st dot com 2006-10-03 16:06 ` pinskia at gcc dot gnu dot org 2006-10-03 16:11 ` pinskia at gcc dot gnu dot org [this message] 2006-10-05 8:15 ` [Bug tree-optimization/29333] Jump threading getting in the way of PHI-OPT roberto dot costa at st dot com [not found] <bug-29333-4@http.gcc.gnu.org/bugzilla/> 2012-01-21 8:17 ` pinskia at gcc dot gnu.org 2012-01-21 8:24 ` pinskia at gcc dot gnu.org 2012-01-22 9:01 ` pinskia at gcc dot gnu.org 2012-01-22 23:45 ` pinskia at gcc dot gnu.org 2012-01-23 10:35 ` rguenth at gcc dot gnu.org 2021-07-06 4:39 ` pinskia at gcc dot gnu.org 2021-11-16 2:15 ` 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=20061003161126.12146.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).