public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at kss-loka dot si" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24073] (vector float){a, b, 0, 0} code gen is not good
Date: Tue, 27 Sep 2005 11:19:00 -0000	[thread overview]
Message-ID: <20050927111921.20259.qmail@sourceware.org> (raw)
In-Reply-To: <20050927040602.24073.pinskia@gcc.gnu.org>


------- Additional Comments From uros at kss-loka dot si  2005-09-27 11:19 -------
With a couple of months old mainline gcc (20050716), following asm is produced:
(-O2 -msse2 -fomit-frame-pointer):

	subl	$12, %esp
	movss	b, %xmm0
	movss	a, %xmm1
	unpcklps	%xmm0, %xmm1
	movaps	%xmm1, %xmm0
	xorl	%eax, %eax
	xorl	%edx, %edx
	movl	%eax, (%esp)
	movl	%edx, 4(%esp)
>>>	movlps	(%esp), %xmm1
	addl	$12, %esp
	movlhps	%xmm1, %xmm0
	ret

This explains where all those xor and moves come from. It looks that newer 
compilers somehow fix the damage by using xorps, a bit late in the game, IMO.

This part of bug depends on PR target/22076.

Other than that, the problem is that V4SF vector initialization is decomposed 
to two V2SF initializations (these are MMX insns and this further confuses 
x87/MMX switching patch) that are later concated to V4SF.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |22076


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


  parent reply	other threads:[~2005-09-27 11:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27  4:06 [Bug target/24073] New: " pinskia at gcc dot gnu dot org
2005-09-27  4:06 ` [Bug target/24073] " pinskia at gcc dot gnu dot org
2005-09-27  4:22 ` pinskia at gcc dot gnu dot org
2005-09-27  5:09 ` pinskia at gcc dot gnu dot org
2005-09-27  5:51 ` belyshev at depni dot sinp dot msu dot ru
2005-09-27 11:19 ` uros at kss-loka dot si [this message]
2005-09-27 11:41 ` uros at kss-loka dot si
2005-09-27 14:34 ` pinskia at gcc dot gnu dot org
     [not found] <bug-24073-6528@http.gcc.gnu.org/bugzilla/>
2006-08-23 21:24 ` stuart at apple dot com
2006-08-23 21:54 ` stuart at apple dot com
     [not found] <bug-24073-4@http.gcc.gnu.org/bugzilla/>
2021-08-21 21:28 ` 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=20050927111921.20259.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).