public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104757] [12 Regression] ICE (segfault) GIMPLE pass: walloca - in gimple_range_global Date: Wed, 02 Mar 2022 11:19:24 +0000 [thread overview] Message-ID: <bug-104757-4-T6UOluaqVM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104757-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104757 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- The reason for the nvptx dependency is the following. omp_max_simt_vf (void) { if (!optimize) return 0; if (ENABLE_OFFLOADING) for (const char *c = getenv ("OFFLOAD_TARGET_NAMES"); c;) { if (startswith (c, "nvptx")) return 32; ... return 0; } * * * Reduced testcase: module m implicit none (external, type) integer :: ll !$omp declare target (ll) contains subroutine foo (i1) !$omp declare target (foo) logical :: i1 integer :: i !$omp distribute simd if(i1) do i = 1, 64 ll = ll +1 end do end end module
next prev parent reply other threads:[~2022-03-02 11:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-02 11:06 [Bug middle-end/104757] New: " burnus at gcc dot gnu.org 2022-03-02 11:14 ` [Bug middle-end/104757] " tschwinge at gcc dot gnu.org 2022-03-02 11:19 ` burnus at gcc dot gnu.org [this message] 2022-03-02 11:25 ` burnus at gcc dot gnu.org 2022-03-02 11:52 ` rguenth at gcc dot gnu.org 2022-03-02 11:52 ` rguenth at gcc dot gnu.org 2022-03-02 15:50 ` burnus at gcc dot gnu.org 2022-03-02 15:57 ` burnus at gcc dot gnu.org 2022-03-02 17:37 ` [Bug middle-end/104757] [12 Regression][OpenMP] ICE in GIMPLE pass: walloca - in gimple_range_global / segfault as SSA_NAME_DEF_STMT is NULL for 'if' clause arg jakub at gcc dot gnu.org 2022-03-02 18:37 ` jakub at gcc dot gnu.org 2022-03-02 18:50 ` jakub at gcc dot gnu.org 2022-03-03 8:22 ` cvs-commit at gcc dot gnu.org 2022-03-03 8:35 ` jakub at gcc dot gnu.org 2022-03-03 14:35 ` tschwinge 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-104757-4-T6UOluaqVM@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).