public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/103836] New: '-fcompare-debug' failure (length) w/ -fopenacc --param openacc-kernels=decompose Date: Sun, 26 Dec 2021 16:17:44 +0000 [thread overview] Message-ID: <bug-103836-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103836 Bug ID: 103836 Summary: '-fcompare-debug' failure (length) w/ -fopenacc --param openacc-kernels=decompose Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: openacc Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Created attachment 52061 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52061&action=edit diff -u o5cia6mf.*.gkd g++ 12.0.0 20211219 snapshot (g:fcbf94a5be9e0c1ecad92da773a6632b86b7f70a) fails -fcompare-debug check when compiling the following testcase w/, extracted from gcc/testsuite/c-c++-common/goacc/nesting-1.c, w/ -fopenacc --param openacc-kernels=decompose: extern int i; void f_acc_kernels (void) { #pragma acc kernels { #pragma acc loop for (i = 0; i < 2; ++i) ; } } % x86_64-unknown-linux-gnu-g++-12.0.0 -O1 -fcompare-debug -fopenacc --param openacc-kernels=decompose -c o5cia6mf.c x86_64-unknown-linux-gnu-g++-12.0.0: error: o5cia6mf.c: '-fcompare-debug' failure (length) Diff between two gkd files attached. I can reproduce the issue only w/ C++ front-end.
next reply other threads:[~2021-12-26 16:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-26 16:17 asolokha at gmx dot com [this message] 2021-12-27 13:18 ` [Bug debug/103836] " jakub at gcc dot gnu.org 2021-12-28 10:45 ` [Bug middle-end/103836] " marxin at gcc dot gnu.org 2022-03-04 13:25 ` 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-103836-4@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).