public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/49588] DATA statement with vector sections rejected (ICE: TODO) Date: Tue, 22 Aug 2023 08:03:13 +0000 [thread overview] Message-ID: <bug-49588-4-PHoZDPAmDu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49588-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49588 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:d3b5a1bccc219680dc19281b6fd6cc798bb679eb commit r14-3380-gd3b5a1bccc219680dc19281b6fd6cc798bb679eb Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Aug 21 21:23:57 2023 +0200 Fortran: implement vector sections in DATA statements [PR49588] gcc/fortran/ChangeLog: PR fortran/49588 * data.cc (gfc_advance_section): Derive next index set and next offset into DATA variable also for array references using vector sections. Use auxiliary array to keep track of offsets into indexing vectors. (gfc_get_section_index): Set up initial indices also for DATA variables with array references using vector sections. * data.h (gfc_get_section_index): Adjust prototype. (gfc_advance_section): Likewise. * resolve.cc (check_data_variable): Pass vector offsets. gcc/testsuite/ChangeLog: PR fortran/49588 * gfortran.dg/data_vector_section.f90: New test.
next prev parent reply other threads:[~2023-08-22 8:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-30 8:53 [Bug fortran/49588] New: " burnus at gcc dot gnu.org 2013-06-26 17:56 ` [Bug fortran/49588] " dominiq at lps dot ens.fr 2023-08-20 20:30 ` anlauf at gcc dot gnu.org 2023-08-21 19:50 ` anlauf at gcc dot gnu.org 2023-08-22 8:03 ` cvs-commit at gcc dot gnu.org [this message] 2023-08-22 18:21 ` anlauf 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-49588-4-PHoZDPAmDu@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).