public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102430] [9/10/11/12 Regression] ICE in fold_convert_loc, at fold-const.c:2554 since r7-4447-gb4c3a85be9658537 Date: Mon, 27 Sep 2021 14:44:02 +0000 [thread overview] Message-ID: <bug-102430-4-sLleXlgzXN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102430-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102430 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The OMP_CLAUSE_LINEAR_ARRAY support is there only for simd constructs (and those are even simpler because we mostly punt on optimizing them by forcing vf of 1). The above mentioned commit was the "Partial OpenMP 4.5 fortran support" patch, which enabled linear clause on do but apparently didn't actually add support for array or allocatable linear. The support for linear on worksharing-loops is done in omp-expand.c (in 3 places expand_omp_for_generic, expand_omp_for_static_nochunk, expand_omp_for_static_chunk) and needs to be added to those. Whether it can use omp_clause_linear_ctor langhook or not is unclear (or whether it needs to be done somehow during omp-low.c instead of omp-expand.c). So, for release branches I think the best would be to sorry on OMP_CLAUSE_LINEAR_ARRAY clauses on OMP_FOR (e.g. in the FE).
next prev parent reply other threads:[~2021-09-27 14:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-21 19:15 [Bug fortran/102430] New: ICE in fold_convert_loc, at fold-const.c:2554 gscfq@t-online.de 2021-09-27 13:10 ` [Bug fortran/102430] [9/10/11/12 Regression] ICE in fold_convert_loc, at fold-const.c:2554 since r7-4447-gb4c3a85be9658537 marxin at gcc dot gnu.org 2021-09-27 14:44 ` jakub at gcc dot gnu.org [this message] 2021-11-05 13:23 ` rguenth at gcc dot gnu.org 2022-01-17 13:28 ` rguenth at gcc dot gnu.org 2022-05-27 9:46 ` [Bug fortran/102430] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 10:41 ` [Bug fortran/102430] [11/12/13/14 " rguenth 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-102430-4-sLleXlgzXN@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).