public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yuri Gribov <tetra2005@gmail.com>
To: Mike Stump <mikestump@comcast.net>
Cc: David Malcolm <dmalcolm@redhat.com>,
	Thomas Preudhomme <thomas.preudhomme@foss.arm.com>,
		GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Ignore random output from Asan tests in dg-cmp-results
Date: Tue, 11 Jul 2017 06:51:00 -0000	[thread overview]
Message-ID: <CAJOtW+63V_vf38LBn4+b4Pxz+r-jaU_qQbO6VRE2CytjCELXdg@mail.gmail.com> (raw)
In-Reply-To: <9F9564B6-973E-4A35-948F-49A5BCFD2511@comcast.net>

On Mon, Jul 10, 2017 at 10:52 PM, Mike Stump <mikestump@comcast.net> wrote:
> On Jul 10, 2017, at 2:21 PM, Mike Stump <mikestump@comcast.net> wrote:
>>
>> Someone with such a system will have to drill down into why.
>
> Found it, fixed in dejagnu 1.5.3, just use a newer dejagnu, 1.5.3 or later should be fine.
>
> Apparently, I should have just checked it _first_.  I didn't expect the fix to lie there.

Thanks, Mike,

I didn't realize that the core issue is in Dejagnu. I believe Richard
fixed it in https://git.linaro.org/toolchain/dejagnu.git/commit/?h=dejagnu-1.5.3-release&id=a78bb783097d8a32dbaa0fe4f3a0d20297e5da15
, at the same time he fixed asan-gtest in GCC.

-Y

  reply	other threads:[~2017-07-11  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 19:06 Yuri Gribov
2017-07-10  9:32 ` Thomas Preudhomme
2017-07-10  9:44   ` Yuri Gribov
2017-07-10 21:21     ` Mike Stump
2017-07-10 21:53       ` Mike Stump
2017-07-11  6:51         ` Yuri Gribov [this message]
2017-07-10 12:13 ` Thomas Preudhomme
2017-07-10 12:32   ` Yuri Gribov
2017-07-10 18:27 ` Mike Stump

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=CAJOtW+63V_vf38LBn4+b4Pxz+r-jaU_qQbO6VRE2CytjCELXdg@mail.gmail.com \
    --to=tetra2005@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=thomas.preudhomme@foss.arm.com \
    /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).