public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/101551] New: [offloading] Differences in diagnostics etc. Date: Wed, 21 Jul 2021 12:34:12 +0000 [thread overview] Message-ID: <bug-101551-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101551 Bug ID: 101551 Summary: [offloading] Differences in diagnostics etc. Product: gcc Version: unknown Status: UNCONFIRMED Keywords: openacc, openmp Severity: minor Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: tschwinge at gcc dot gnu.org CC: burnus at gcc dot gnu.org, jakub at gcc dot gnu.org Target Milestone: --- There are differences in diagnostics etc. depending on whether offloading is disabled or enabled, as we already had found in <http://mid.mail-archive.com/87pmyg4y9s.fsf@euler.schwinge.homeip.net> "openacc: Warnings for strange partitioning choices for parallel regions" and following. Additionally, I just noticed that calling 'lang_hooks.decl_printable_name (current_function_decl, 2)' in 'gcc/omp-offload.c:execute_oacc_device_lower' for an OpenACC 'routine' 'void ROUTINE (float)', for C that returns 'ROUTINE', for C++ 'ROUTINE(float)' for offloading enabled and 'void ROUTINE(float)' otherwise (notice difference regarding return type), for corresponding Fortran 'routine_' for offloading enabled and 'routine' otherwise (notice difference in '_' suffix). Low priority certainly, but would be nice to fix/unify at some point, because this occasionally necessitates special care when writing testcases.
next reply other threads:[~2021-07-21 12:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-21 12:34 tschwinge at gcc dot gnu.org [this message] 2021-07-21 13:01 ` [Bug middle-end/101551] " tschwinge at gcc dot gnu.org 2021-09-06 13:42 ` tschwinge at gcc dot gnu.org 2022-07-12 6:28 ` 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-101551-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).