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 ED17D3896142; Tue, 26 May 2020 10:15:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED17D3896142
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1590488122;
 bh=5359fN2T3L+41M3jXe5j3Z8764ALpX7Q1lWem3XHzxU=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=Wnyzuu6GJTM9rXEC22GKpSTU4maTOJvphtLlg6Yzr0USOjpJCPwYl9HOQJ1DzzCV3
 WJlH8zIsE/5j+olhvVJvd4QNDMbsqxYS6wzmX5ICw70d+UFktGA4LMr/6OeZbSvRY2
 Aa3yJ5g8ECCNd/2eKbaEL9SZmgWAwmIyBaf/lA74=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77691] [8/9/10/11 regression]
 experimental/memory_resource/resource_adaptor.cc FAILs
Date: Tue, 26 May 2020 10:15:22 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: ro at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-77691-4-EtrGw1EAa7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77691-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77691-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: <http://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: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 26 May 2020 10:15:23 -0000

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

--- Comment #43 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Alexandre Oliva
<aoliva@gcc.gnu.org>:

https://gcc.gnu.org/g:b425be2c4c6763436d63543501c6762ae031e43c

commit r10-8186-gb425be2c4c6763436d63543501c6762ae031e43c
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed May 13 05:21:42 2020 -0300

    x86-vxworks malloc aligns to 8 bytes like solaris

    Vxworks 7's malloc, like Solaris', only ensures 8-byte alignment of
    returned pointers on 32-bit x86, though GCC's stddef.h defines
    max_align_t with 16-byte alignment for __float128.  This patch enables
    on x86-vxworks the same memory_resource workaround used for x86-solaris.

    The testsuite also had a workaround, defining BAD_MAX_ALIGN_T and
    xfailing the test; extend those to x86-vxworks as well, and remove the
    check for char-aligned requested allocation to be aligned like
    max_align_t.  With that change, the test passes on x86-vxworks; I'm
    guessing that's the same reason for the test not to pass on
    x86-solaris (and on x86_64-solaris -m32), so with the fix, I'm
    tentatively removing the xfail.


    for libstdc++-v3/ChangeLog

            PR libstdc++/77691
            * include/experimental/memory_resource
            (__resource_adaptor_imp::do_allocate): Handle max_align_t on
            x86-vxworks as on x86-solaris.
            (__resource_adaptor_imp::do_deallocate): Likewise.
            * testsuite/experimental/memory_resource/new_delete_resource.cc:
            Drop xfail.
            (BAD_MAX_ALIGN_T): Define on x86-vxworks as on x86-solaris.
            (test03): Drop max-align test for char-aligned alloc.

    (cherry picked from commit 883246530f1bb10d854f455e1c3d55b93675690a)=