From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-399367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 13022 invoked by alias); 23 Aug 2012 17:16:50 -0000
Received: (qmail 13006 invoked by uid 22791); 23 Aug 2012 17:16:48 -0000
X-SWARE-Spam-Status: No, hits=-4.3 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Aug 2012 17:16:24 +0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/54342] [4.8 Regression] Wrong mode of call argument
Date: Thu, 23 Aug 2012 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.0
X-Bugzilla-Changed-Fields: Status
Message-ID: <bug-54342-4-ZyraoPrh27@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54342-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-08/txt/msg01639.txt.bz2

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> 2012-08-23 17:16:21 UTC ---
(In reply to comment #8)
> I don't think AVX supports true 256-bit integer. On the other hand, I was
> also puzzled by compute_record_mode, which excludes UNION_TYPE and
> QUAL_UNION_TYPE.  Will including them break union?

It breaks gcc.c-torture/compile/pr42196-2.c:

union U
{
  __complex__ int ci;
  __complex__ float cf;
};

float gd;
extern float bar (union U);

float foo (int b, double f1, double f2, int c1, int c2)
{
  union U u;
  double r;

  if (b)
    {
      __real__ u.cf = f1;
      __imag__ u.cf = f2;
    }
  else
    {
      __real__ u.ci = c1;
      __imag__ u.ci = c2;
    }

  r = bar (u);
  return r;
}

The proper fix is to allow OImode in your case without adding it to
VALID_AVX256_REG_MODE.