public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: Tobias Burnus <tobias@codesourcery.com>,
	Jakub Jelinek <jakub@redhat.com>
Cc: gcc-regression@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [r12-4725 Regression] FAIL: libgomp.c/doacross-1.c (test for excess errors) on Linux/x86_64
Date: Wed, 27 Oct 2021 10:06:38 -0600	[thread overview]
Message-ID: <bd591713-87e5-69e9-c3b5-360a279ffccd@gmail.com> (raw)
In-Reply-To: <af27815b-8385-085a-9d24-666d6a4e722a@codesourcery.com>

On 10/27/21 9:48 AM, Tobias Burnus wrote:
> On 27.10.21 17:36, Martin Sebor via Gcc-patches wrote:
> 
>> On 10/27/21 7:30 AM, Jakub Jelinek wrote:
>>> On Tue, Oct 26, 2021 at 10:22:19PM -0700, sunil.k.pandey via
>>> Gcc-patches wrote:
>>>> FAIL: libgomp.c/doacross-1.c (test for excess errors)
>>
>> I don't see this failure in my logs (or the other one) or any
>> evidence of the libhomp tests having run.  Does the libgomp
>> test suite need something special to enable?
> 
> I don't know whether it can be disabled - but I bet you have build
> libgomp. Thus:
> 
> Did you run "make check" in the main build directory or in $(BUILD)/gcc?
> – only the former runs it.

Thanks.  I figured out why I didn't see it.  I was looking at
the wrong log file, one from testing just the one patch for
the atomic built-ins, rather than the one for all three that
I pushed yesterday (including the one to make a greater use
of the ranger).  The warning only shows with all of them
applied.

Martin

> 
> You can run it directly (from the main $(BUILD) dir) as "make
> check-target-libgomp" – or just got to $(BUILD)/*/libgomp/ and run "make
> check" there. – In the latter directory, you an also use RUNTESTFLAGS=
> to run only a specific test.
> 
> (The * above is the target triplet; here, it is x86_64-pc-linux-gnu.)
> 
> Besides libgomp, there are some other libraries with testsuites outside
> gcc/testsuite, like libstdc++-v3/testsuite or libatomic/testsuite or ...
> 
> Tobias
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 
> 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: 
> Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; 
> Registergericht München, HRB 106955



      reply	other threads:[~2021-10-27 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27  5:22 sunil.k.pandey
2021-10-27 13:30 ` Jakub Jelinek
2021-10-27 15:36   ` Martin Sebor
2021-10-27 15:48     ` Tobias Burnus
2021-10-27 16:06       ` Martin Sebor [this message]

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=bd591713-87e5-69e9-c3b5-360a279ffccd@gmail.com \
    --to=msebor@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=tobias@codesourcery.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).