public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug boehm-gc/64042] FAIL: boehm-gc.c/gctest.c -O2 execution test Date: Tue, 02 Dec 2014 08:57:00 -0000 [thread overview] Message-ID: <bug-64042-4-QoUWfJb4F8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64042-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64042 --- Comment #5 from vries at gcc dot gnu.org --- An easy way to reproduce, is to add this patch: ... diff -u /home/vries/gcc_versions/data/ref-master-14-12-02/src/boehm-gc/testsuite/boehm-gc.c/c.exp ./c.exp --- /home/vries/gcc_versions/data/ref-master-14-12-02/src/boehm-gc/testsuite/boehm-gc.c/c.exp 2014-12-02 02:51:25.000000000 +0100 +++ ./c.exp 2014-11-26 14:39:41.964962842 +0100 @@ -19,4 +19,8 @@ boehm-gc-dg-runtest [lsort [glob -nocomplain $srcdir/$subdir/*.c]] "-O2" "" +for {set i 0} {$i < 1000} {incr i} { + boehm-gc-dg-runtest [lsort [glob -nocomplain $srcdir/$subdir/gctest.c]] "-O2" "" +} + dg-finish ... This way (1000 * compile/run) it triggered twice for me.
next prev parent reply other threads:[~2014-12-02 8:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-24 9:32 [Bug boehm-gc/64042] New: " vries at gcc dot gnu.org 2014-11-24 9:33 ` [Bug boehm-gc/64042] " vries at gcc dot gnu.org 2014-11-24 9:39 ` vries at gcc dot gnu.org 2014-11-24 10:12 ` vries at gcc dot gnu.org 2014-11-25 21:20 ` vries at gcc dot gnu.org 2014-12-02 8:57 ` vries at gcc dot gnu.org [this message] 2015-01-13 16:33 ` vries at gcc dot gnu.org 2015-01-13 16:56 ` hjl.tools at gmail dot com 2015-01-13 18:10 ` law at redhat dot com 2015-01-16 12:06 ` vries at gcc dot gnu.org 2015-01-17 20:45 ` iains at gcc dot gnu.org 2015-01-20 11:06 ` vries 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-64042-4-QoUWfJb4F8@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: linkBe 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).