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 target/11877] gcc should use xor trick with -Os
Date: Sun, 04 Jan 2004 07:50:00 -0000	[thread overview]
Message-ID: <20040104075048.17594.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030810154728.11877.debian-gcc@lists.debian.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-04 07:50 -------
What about expanding (set (mem:DI ...) (const_int 0)) at expand time, this will cause more 
opportunities to happen and then the discusion is up to other parts of the compiler.
It looks like an easy change to ix86_expand_move.
Also interesting is that this testcase:
void
foo (long *p)
{
  *p = 0;
  p[1] = 0;
}
Does not use the xor trick either.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11877


  parent reply	other threads:[~2004-01-04  7:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10 15:47 [Bug target/11877] New: " debian-gcc at lists dot debian dot org
2003-08-10 16:03 ` [Bug target/11877] " pinskia at gcc dot gnu dot org
2003-08-23  1:15 ` dhazeghi at yahoo dot com
2003-12-31 21:39 ` kazu at cs dot umass dot edu
2004-01-04  6:55 ` kazu at cs dot umass dot edu
2004-01-04  7:50 ` pinskia at gcc dot gnu dot org [this message]
2004-02-01 17:24 ` kazu at cs dot umass dot edu
2004-03-25 19:16 ` kazu at cs dot umass dot edu
2005-08-12  5:28 ` pinskia at gcc dot gnu dot org
2005-08-12  5:28 ` pinskia at gcc dot gnu dot org
     [not found] <bug-11877-5724@http.gcc.gnu.org/bugzilla/>
2006-01-05 20:22 ` dann at godzilla dot ics dot uci dot edu
     [not found] <bug-11877-4@http.gcc.gnu.org/bugzilla/>
2021-06-21  7:56 ` cvs-commit at gcc dot gnu.org
2021-06-22  8:18 ` cvs-commit at gcc dot gnu.org
2021-07-10  8:24 ` roger at nextmovesoftware dot com
2021-07-26 18:54 ` pinskia at gcc dot gnu.org
2021-07-26 18:57 ` pinskia at gcc dot gnu.org
2021-07-26 22:20 ` 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=20040104075048.17594.qmail@sources.redhat.com \
    --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).