public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/94609] FAIL: gdc.dg/runnable.d
Date: Thu, 16 Apr 2020 00:26:32 +0000	[thread overview]
Message-ID: <bug-94609-4-X0Z18wKabV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94609-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to H.J. Lu from comment #9)
> 
> I tested with glibc 2.30 with fix for
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=25810
> 

Nice, though currently the library testsuite is compiled at -O0.  I want to
turn on -O2 however, which causes many x32 tests to start failing, some with
very hard to debug reasons.


> I got
> 
> FAIL: libphobos.phobos_shared/std/algorithm/mutation.d execution test
> FAIL: libphobos.phobos_shared/std/algorithm/mutation.d execution test
> FAIL: libphobos.phobos_shared/std/algorithm/mutation.d execution test
> FAIL: libphobos.phobos_shared/std/conv.d execution test
> FAIL: libphobos.phobos_shared/std/conv.d execution test
> FAIL: libphobos.phobos_shared/std/conv.d execution test
> FAIL: libphobos.phobos_shared/std/datetime/systime.d execution test
> FAIL: libphobos.phobos_shared/std/datetime/systime.d execution test
> FAIL: libphobos.phobos_shared/std/datetime/systime.d execution test
> FAIL: libphobos.phobos_shared/std/range/primitives.d (test for excess errors)
> FAIL: libphobos.phobos/std/algorithm/mutation.d execution test
> FAIL: libphobos.phobos/std/algorithm/mutation.d execution test
> FAIL: libphobos.phobos/std/algorithm/mutation.d execution test
> FAIL: libphobos.phobos/std/conv.d execution test
> FAIL: libphobos.phobos/std/conv.d execution test
> FAIL: libphobos.phobos/std/conv.d execution test
> FAIL: libphobos.phobos/std/datetime/systime.d execution test
> FAIL: libphobos.phobos/std/datetime/systime.d execution test
> FAIL: libphobos.phobos/std/datetime/systime.d execution test
> FAIL: libphobos.phobos/std/range/primitives.d (test for excess errors)
> 
> with
> 
> $ make check RUNTESTFLAGS="--target_board='unix{-mx32,-m32,}'"

I've seen this too.  If nested structs are to be passed by invisible reference
now, we still need copy semantics if there is no defined cpctor or dtor.

I'm just thinking about the best location to handle this.  Will have something
by morning after running it by the testsuite again.

  parent reply	other threads:[~2020-04-16  0:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 18:38 [Bug d/94609] New: " hjl.tools at gmail dot com
2020-04-15 20:24 ` [Bug d/94609] " ibuclaw at gdcproject dot org
2020-04-15 20:25 ` hjl.tools at gmail dot com
2020-04-15 20:32 ` ibuclaw at gdcproject dot org
2020-04-15 20:42 ` ibuclaw at gdcproject dot org
2020-04-15 20:57 ` ibuclaw at gdcproject dot org
2020-04-15 21:03 ` hjl.tools at gmail dot com
2020-04-15 21:07 ` ibuclaw at gdcproject dot org
2020-04-15 21:09 ` ibuclaw at gdcproject dot org
2020-04-15 23:47 ` hjl.tools at gmail dot com
2020-04-15 23:54 ` hjl.tools at gmail dot com
2020-04-16  0:26 ` ibuclaw at gdcproject dot org [this message]
2020-04-16  7:41 ` ibuclaw at gdcproject dot org
2020-04-19  8:08 ` cvs-commit at gcc dot gnu.org
2020-04-19  8:11 ` ibuclaw at gdcproject dot org
2020-04-19 14:24 ` cvs-commit 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=bug-94609-4-X0Z18wKabV@http.gcc.gnu.org/bugzilla/ \
    --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).