public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fjahanian at apple dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/18916] [4.0 Regression] mis-aligned vector code with copy memory (-maltivec)
Date: Wed, 29 Dec 2004 17:34:00 -0000	[thread overview]
Message-ID: <20041229173406.1304.qmail@sourceware.org> (raw)
In-Reply-To: <20041210010826.18916.fjahanian@apple.com>


------- Additional Comments From fjahanian at apple dot com  2004-12-29 17:34 -------

(In reply to comment #8)
> Why can't we make sure that temporaries which should be aligned to 128 bits are actually aligned to 
> 128 bits?  Surely failing to do so will cause other problems.

Yes, this is the best way of fixing this problem, hoping not to break ABI conformacne in some obscure
way along the way. My last posted patch, took the approach of setting the alignment of the
stack temporaries to what they really were. This worked, but it also turned off the Vector move insns
for such temporaries. I will look at forcing the 128 bit alignment next year.

-- 


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


  parent reply	other threads:[~2004-12-29 17:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  1:08 [Bug target/18916] New: vector code is generated to copy data to mis-aligned memory (-mcpu=G5) fjahanian at apple dot com
2004-12-10  1:12 ` [Bug target/18916] " fjahanian at apple dot com
2004-12-10  1:27 ` pinskia at gcc dot gnu dot org
2004-12-10  1:42 ` fjahanian at apple dot com
2004-12-10  3:21 ` dje at gcc dot gnu dot org
2004-12-10  3:35 ` pinskia at gcc dot gnu dot org
2004-12-10  3:35 ` [Bug target/18916] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-14  1:48 ` [Bug target/18916] [4.0 Regression] vector code is generated to copy data to mis-aligned memory (-maltivec) pinskia at gcc dot gnu dot org
2004-12-18  0:43 ` [Bug target/18916] [4.0 Regression] mis-aligned vector code with copy " fjahanian at apple dot com
2004-12-18  1:46 ` fjahanian at apple dot com
2004-12-21  1:25 ` fjahanian at apple dot com
2004-12-28 23:05 ` geoffk at gcc dot gnu dot org
2004-12-29 17:34 ` fjahanian at apple dot com [this message]
2004-12-31 23:15 ` amodra at bigpond dot net dot au
2005-01-01  7:17 ` amodra at bigpond dot net dot au
2005-01-07 23:39 ` amodra at bigpond dot net dot au
2005-01-11  9:52 ` cvs-commit at gcc dot gnu dot org
2005-01-11 10:03 ` amodra at bigpond dot net dot au

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=20041229173406.1304.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).