public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/33349] Redundant zero-extension of registers Date: Fri, 06 Feb 2009 21:45:00 -0000 [thread overview] Message-ID: <20090206214516.30683.qmail@sourceware.org> (raw) In-Reply-To: <bug-33349-8549@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from steven at gcc dot gnu dot org 2009-02-06 21:45 ------- This would be fixed if someone would fix the Sign Extension Elimination pass (yes, it also handles zero extensions). But that pass is probably broken beyond repair at this point, and likely needs a rewrite instead of just a fix. -- steven 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 |2009-02-06 21:45:16 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33349
next prev parent reply other threads:[~2009-02-06 21:45 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-08 3:07 [Bug c++/33349] New: " us15 at os dot inf dot tu-dresden dot de 2009-02-06 21:45 ` steven at gcc dot gnu dot org [this message] [not found] <bug-33349-4@http.gcc.gnu.org/bugzilla/> 2011-06-16 11:28 ` [Bug middle-end/33349] " gcc.hall at gmail dot com
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=20090206214516.30683.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).