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/26069] [4.1/4.2/4.3 Regression] Runtime endian-ness check is no longer optimized out.
Date: Wed, 30 Apr 2008 03:48:00 -0000 [thread overview]
Message-ID: <20080430034722.31499.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26069-12114@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from pinskia at gcc dot gnu dot org 2008-04-30 03:47 -------
(In reply to comment #21)
> (In reply to comment #20)
>
> > Here are 2 alternatives I've been playing with:
>
> Any news on this patch?
The second patch looks like what is was done on the RTL level with respect of
DSE. I am testing a patch to tree-ssa-forwprop that adds folding where the
sizes of the types are the same to use VIEW_CONVERT_EXPR. This will allow us
to do the correct thing on the tree level for comment #11. Note we don't
convert it to a NOP_EXPR yet because it creates invalid gimple. It also allows
us to "fixup" aliasing issues where the types are the same size so we will get
less bug reports about those cases.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26069
next prev parent reply other threads:[~2008-04-30 3:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 5:00 [Bug rtl-optimization/26069] New: " atgraham at gmail dot com
2006-02-02 5:02 ` [Bug rtl-optimization/26069] " atgraham at gmail dot com
2006-02-02 5:19 ` [Bug rtl-optimization/26069] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-02-02 14:56 ` rguenth at gcc dot gnu dot org
2006-02-03 11:55 ` rguenth at gcc dot gnu dot org
2006-02-06 10:34 ` rguenth at gcc dot gnu dot org
2006-02-06 16:53 ` gianni at mariani dot ws
2006-02-14 8:59 ` mmitchel at gcc dot gnu dot org
2006-02-24 0:30 ` mmitchel at gcc dot gnu dot org
2006-04-18 16:22 ` bonzini at gnu dot org
2006-05-25 2:39 ` mmitchel at gcc dot gnu dot org
2006-08-26 6:42 ` pinskia at gcc dot gnu dot org
2006-08-26 14:40 ` pinskia at gcc dot gnu dot org
2006-08-26 16:41 ` pinskia at gcc dot gnu dot org
2006-08-26 16:51 ` pinskia at gcc dot gnu dot org
2006-08-26 23:04 ` pinskia at gcc dot gnu dot org
2006-08-26 23:21 ` pinskia at gcc dot gnu dot org
2006-09-05 1:09 ` patchapp at dberlin dot org
2006-12-27 4:35 ` [Bug rtl-optimization/26069] [4.0/4.1/4.2/4.3 " pinskia at gcc dot gnu dot org
2007-02-14 9:11 ` mmitchel at gcc dot gnu dot org
2007-05-27 19:39 ` pinskia at gcc dot gnu dot org
2007-11-03 18:11 ` pinskia at gcc dot gnu dot org
2007-12-03 13:09 ` jakub at gcc dot gnu dot org
2008-02-21 21:55 ` [Bug tree-optimization/26069] [4.0/4.1/4.2/4.3/4.4 " ubizjak at gmail dot com
2008-03-25 3:43 ` [Bug tree-optimization/26069] [4.0/4.1/4.2/4.3 " pinskia at gcc dot gnu dot org
2008-04-30 3:48 ` pinskia at gcc dot gnu dot org [this message]
2008-04-30 3:59 ` [Bug tree-optimization/26069] [4.1/4.2/4.3 " pinskia at gcc dot gnu dot org
2008-04-30 4:06 ` pinskia at gcc dot gnu dot org
2008-04-30 4:14 ` pinskia at gcc dot gnu dot org
2008-04-30 9:26 ` pinskia at gcc dot gnu dot org
2008-07-04 20:19 ` [Bug tree-optimization/26069] [4.2/4.3 " jsm28 at gcc dot gnu dot org
2009-03-31 19:10 ` [Bug tree-optimization/26069] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:35 ` rguenth at gcc dot gnu dot org
2010-04-20 13:05 ` rguenth 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=20080430034722.31499.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: link
Be 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).