RE: [EXTERNAL] RE: [r13-3172 Regression] FAIL:libgomp.oacc-c../../libgomp.oacc-c-c..-common/kernels-loop-g.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (test for excess errors) on Linux/x86_64

public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed

From: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: "haochen.jiang@intel.com" <haochen.jiang@intel.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"gcc-regression@gcc.gnu.org" <gcc-regression@gcc.gnu.org>
Subject: RE: [EXTERNAL] RE: [r13-3172 Regression] FAIL:libgomp.oacc-c../../libgomp.oacc-c-c..-common/kernels-loop-g.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (test for excess errors) on Linux/x86_64
Date: Mon, 17 Oct 2022 14:54:15 +0000	[thread overview]
Message-ID: <CY5PR21MB3542C5FA53CB7CA8AEB84E2D91299@CY5PR21MB3542.namprd21.prod.outlook.com> (raw)
In-Reply-To: <87fsfmsp84.fsf@euler.schwinge.homeip.net>

Yes, I received that one. The root cause is the -gstatement-frontiers issue https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100733 . I submitted a workaround patch for that ( https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603673.html ) but it hasn't been approved yet. Another workaround is passing -gno-statement-frontiers to the test.

Eugene

-----Original Message-----
From: Thomas Schwinge <thomas@codesourcery.com> 
Sent: Monday, October 17, 2022 3:46 AM
To: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>
Cc: haochen.jiang@intel.com; gcc-patches@gcc.gnu.org; gcc-regression@gcc.gnu.org
Subject: [EXTERNAL] RE: [r13-3172 Regression] FAIL:libgomp.oacc-c../../libgomp.oacc-c-c..-common/kernels-loop-g.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (test for excess errors) on Linux/x86_64

Hi!

On 2022-10-17T06:11:01+0000, "Jiang, Haochen via Gcc-patches" <gcc-patches@gcc.gnu.org> wrote:
> I just checkout to your commit and the test still got failed.
>
> It is reporting like this:
> xgcc: error: 
> /export/users2/haochenj/src/gcc/master/./libgomp/testsuite/libgomp.oac
> c-c++/../libgomp.oacc-c-c++-common/kernels-loop-g.c: '-fcompare-debug' 
> failure (length)

Right.  I had filed <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.gnu.org%2FPR107231&amp;data=05%7C01%7CEugene.Rozenfeld%40microsoft.com%7C05c1cd8b5db4455fe3de08dab02ce66e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016004172688130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=BfdPnXz5%2Bxr8NwIcBvaOnkFPyzfLQBbyrbMc777EIsk%3D&amp;reserved=0> "[13 Regression]
c-c++-common/goacc/kernels-loop-g.c: '-fcompare-debug' failure (length)"
with you in CC: <erozen@microsoft.com>.  (Have you not received that
one?)


Grüße
 Thomas


> Also fix a typo in manually sending, should be this to reproduce
>
> To reproduce:
>
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m32}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m64}'"
> $ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m64\ -march=cascadelake}'"
>
> BRs,
> Haochen
>
> From: Jiang, Haochen
> Sent: Monday, October 17, 2022 1:41 PM
> To: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>; 
> gcc-patches@gcc.gnu.org; gcc-regression@gcc.gnu.org
> Subject: RE: [r13-3172 Regression] 
> FAIL:libgomp.oacc-c../../libgomp.oacc-c-c..-common/kernels-loop-g.c 
> -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 
> (test for excess errors) on Linux/x86_64
>
> If that has been fixed, just ignore that mail.
>
> It is run through by a script and got the result few days ago. 
> However, the sendmail service was down on that machine and I just 
> noticed that issue. So I sent that result manually today in case that is not fixed.
>
> Sorry for the disturb!
>
> BRs,
> Haochen
>
> From: Eugene Rozenfeld 
> <Eugene.Rozenfeld@microsoft.com<mailto:Eugene.Rozenfeld@microsoft.com>
> >
> Sent: Monday, October 17, 2022 1:23 PM
> To: Jiang, Haochen 
> <haochen.jiang@intel.com<mailto:haochen.jiang@intel.com>>; 
> gcc-patches@gcc.gnu.org<mailto:gcc-patches@gcc.gnu.org>; 
> gcc-regression@gcc.gnu.org<mailto:gcc-regression@gcc.gnu.org>
> Subject: RE: [r13-3172 Regression] 
> FAIL:libgomp.oacc-c../../libgomp.oacc-c-c..-common/kernels-loop-g.c 
> -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 
> (test for excess errors) on Linux/x86_64
>
> That commit had a bug that was fixed in 
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.
> gnu.org%2Fgit%2F%3Fp%3Dgcc.git%3Ba%3Dcommit%3Bh%3D80f414e6d73f9f1683f9
> 3d83ce63a6a482e54bee&amp;data=05%7C01%7CEugene.Rozenfeld%40microsoft.c
> om%7C05c1cd8b5db4455fe3de08dab02ce66e%7C72f988bf86f141af91ab2d7cd011db
> 47%7C1%7C0%7C638016004172688130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLj
> AwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&a
> mp;sdata=50kAEt5C%2F8DO%2BvuyNvE7c1ydxriGeQwY5G%2Bqs%2FgSGE0%3D&amp;re
> served=0
>
> Was that fix included in your GCC build?
>
> From: Jiang, Haochen 
> <haochen.jiang@intel.com<mailto:haochen.jiang@intel.com>>
> Sent: Sunday, October 16, 2022 8:09 PM
> To: gcc-patches@gcc.gnu.org<mailto:gcc-patches@gcc.gnu.org>; Eugene 
> Rozenfeld 
> <Eugene.Rozenfeld@microsoft.com<mailto:Eugene.Rozenfeld@microsoft.com>
> >; Jiang, Haochen 
> <haochen.jiang@intel.com<mailto:haochen.jiang@intel.com>>; 
> gcc-regression@gcc.gnu.org<mailto:gcc-regression@gcc.gnu.org>
> Subject: [EXTERNAL] [r13-3172 Regression] 
> FAIL:libgomp.oacc-c../../libgomp.oacc-c-c..-common/kernels-loop-g.c 
> -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 
> (test for excess errors) on Linux/x86_64
>
> You don't often get email from 
> haochen.jiang@intel.com<mailto:haochen.jiang@intel.com>. Learn why 
> this is important<https://aka.ms/LearnAboutSenderIdentification>
> On Linux/x86_64,
>
> f30e9fd33e56a5a721346ea6140722e1b193db42 is the first bad commit 
> commit f30e9fd33e56a5a721346ea6140722e1b193db42
> Author: Eugene Rozenfeld <erozen@microsoft.com<mailto:erozen@microsoft.com>>
> Date:   Thu Apr 21 16:43:24 2022 -0700
>
>     Set discriminators for call stmts on the same line within the same basic block.
>
> caused
>
> FAIL: libgomp.oacc-c../../libgomp.oacc-c-c..-common/kernels-loop-g.c 
> -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable  -O2  
> (test for excess errors)
>
> with GCC configured with
>
> ../../gcc/configure 
> --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-2288/
> usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld 
> --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet 
> --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
>
> To reproduce:
>
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="c++.exp=libgomp.oacc-c-c++-common/kernels-loop-g.c --target_board='unix{-m64\ -march=cascadelake}'"
-----------------
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

     prev parent reply	other threads:[~2022-10-17 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  3:08 Jiang, Haochen
2022-10-17  5:23 ` Eugene Rozenfeld
2022-10-17  5:40   ` Jiang, Haochen
2022-10-17  6:11     ` Jiang, Haochen
2022-10-17 10:45       ` Thomas Schwinge
2022-10-17 14:54         ` Eugene Rozenfeld [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=CY5PR21MB3542C5FA53CB7CA8AEB84E2D91299@CY5PR21MB3542.namprd21.prod.outlook.com \
    --to=eugene.rozenfeld@microsoft.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    --cc=thomas@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).