From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id D3BDC384BC2C; Mon, 30 May 2022 20:40:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D3BDC384BC2C
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/7061] Access of bytes in struct parameters
Date: Mon, 30 May 2022 20:40:10 +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-Version: 3.2
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-7061-4-KBEs3LJodW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-7061-4@http.gcc.gnu.org/bugzilla/>
References: <bug-7061-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2022 20:40:10 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D7061

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:1ad584d538d349db13cfa8440222d91d5e9aff3f

commit r13-859-g1ad584d538d349db13cfa8440222d91d5e9aff3f
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Mon May 30 21:32:58 2022 +0100

    Allow SCmode and DImode to be tieable with TARGET_64BIT on x86_64.

    This patch is a form of insurance policy in case my patch for PR 7061 r=
uns
    into problems on non-x86 targets; the middle-end can add an extra check
    that the backend is happy placing SCmode and DImode values in the same
    register, before creating a SUBREG.  Unfortunately, ix86_modes_tieable_p
    currently claims this is not allowed(?), even though the default target
    hook for modes_tieable_p is to always return true [i.e. false can be
    used to specifically prohibit bad combinations], and the x86_64 ABI
    passes SCmode values in DImode registers!.  This makes the backend's
    modes_tiable_p hook a little more forgiving, and additionally enables
    interconversion between SCmode and V2SFmode, and between DCmode and
    VD2Fmode, which opens interesting opporutunities in the future.

    2022-05-30  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/ChangeLog
            * config/i386/i386.cc (ix86_modes_tieable_p): Allow SCmode to be
            tieable with DImode on TARGET_64BIT, and SCmode tieable with
            V2SFmode, and DCmode with V2DFmode.=