From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [v3] xfail experimental/memory_resource/resource_adaptor.cc on 32-bit Solaris/x86 (PR libstdc++/77691)
Date: Thu, 22 Mar 2018 13:42:00 -0000 [thread overview]
Message-ID: <yddtvt8i5vu.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20180322115547.GC25691@redhat.com> (Jonathan Wakely's message of "Thu, 22 Mar 2018 11:55:47 +0000")
Hi Jonathan,
> On 22/03/18 11:03 +0100, Rainer Orth wrote:
>>experimental/memory_resource/resource_adaptor.cc currently FAILs on
>>32-bit Solaris/x86:
>>
>>Assertion failed: aligned<max_align_t>(p), file
>> /vol/gcc/src/hg/trunk/local/libstdc++-v3/testsuite/experimental/memory_resource/resource_adaptor.cc,
>> line 56, function test05
>>
>>As detailed in the PR, this happens because Solaris <stddef.h> and the
>>Studio 12.6 compilers know nothing about __float128/_Float128 and malloc
>>only returns pointers aligned to 8 bytes, not 16 bytes as expected by
>>gcc/ginclude/stddef.h (max_align_t).
>>
>>Thus, while checking if Solaris i386 malloc can be changed here, I'm
>>xfailing the test.
>>
>>Tested on i386-pc-solaris2.11, amd64-pc-solaris2.11, and
>>sparc-sun-solaris2.11.
>>
>>Ok for mainline?
>
> OK, thanks.
installed on mainline. I just noticed that the bug is marked as 7
regression; I guess it's ok to backport to the gcc-7 branch, too?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2018-03-22 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 10:04 Rainer Orth
2018-03-22 11:56 ` Jonathan Wakely
2018-03-22 13:42 ` Rainer Orth [this message]
2018-03-22 14:23 ` Jonathan Wakely
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=yddtvt8i5vu.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@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).