public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/101310] Bind(C): CFI_section seems confused by pointer arrays Date: Sat, 17 Jul 2021 20:35:19 +0000 [thread overview] Message-ID: <bug-101310-4-fvAdpiBVLO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101310-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101310 --- Comment #1 from sandra at gcc dot gnu.org --- Looks like 3 bugs for the price of 1! First off the loop to fill in the result dimensions in CFI_section seemed to be applying the base adjustment twice in different ways, or something like that. I've rewritten and simplified that code. The section-3 and section-3p test cases were themselves buggy. I swear I fixed one of bugs before but I must have discarded that change along with some failed experiments/debugging code for the bug above. Finally, fc-out-descriptor-7 was failing because it uses the same pointer array as both source and result, and CFI_section was messing with the dimensions in result before computing the base address adjustment from source. This ended up not having anything to do with the result array being intent(out). I'm going to add some more test cases and regression-test before posting the patch, but I do have fixes for all 3 bugs now.
next prev parent reply other threads:[~2021-07-17 20:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-03 20:48 [Bug libfortran/101310] New: " sandra at gcc dot gnu.org 2021-07-17 20:35 ` sandra at gcc dot gnu.org [this message] 2021-07-18 5:54 ` [Bug libfortran/101310] " sandra at gcc dot gnu.org 2021-07-28 4:25 ` cvs-commit at gcc dot gnu.org 2021-07-28 20:22 ` sandra 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-101310-4-fvAdpiBVLO@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).