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/38497] PRE missing a load PRE which causes a loop to have two BBs Date: Thu, 11 Dec 2008 23:25:00 -0000 [thread overview] Message-ID: <20081211232418.26730.qmail@sourceware.org> (raw) In-Reply-To: <bug-38497-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2008-12-11 23:24 ------- This is a reduced testcase from The huffman byte benchmark. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38497
next prev parent reply other threads:[~2008-12-11 23:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-11 23:22 [Bug tree-optimization/38497] New: " pinskia at gcc dot gnu dot org 2008-12-11 23:25 ` pinskia at gcc dot gnu dot org [this message] 2010-03-02 19:01 ` [Bug tree-optimization/38497] " pinskia at gcc dot gnu dot org 2010-03-03 10:43 ` rguenth at gcc dot gnu dot org 2010-03-03 10:57 ` steven at gcc dot gnu dot org 2010-03-03 11:03 ` rguenth at gcc dot gnu dot org 2010-03-03 14:26 ` steven at gcc dot gnu dot org 2010-05-05 10:31 ` rguenth at gcc dot gnu dot org [not found] <bug-38497-4@http.gcc.gnu.org/bugzilla/> 2021-08-22 4:04 ` 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=20081211232418.26730.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).