From: Harald Anlauf <anlauf@gmx.de>
To: sgk@troutmask.apl.washington.edu,
Harald Anlauf via Fortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, tobias@codesourcery.com
Subject: Re: [PATCH] Fortran: fix CLASS attribute handling [PR106856]
Date: Fri, 3 Mar 2023 22:17:47 +0100 [thread overview]
Message-ID: <7c36addc-00ae-7d75-694b-e47098485e61@gmx.de> (raw)
In-Reply-To: <ZAJROLZ2n2gnvin3@troutmask.apl.washington.edu>
Hi Steve,
Am 03.03.23 um 20:57 schrieb Steve Kargl via Gcc-patches:
> On Thu, Mar 02, 2023 at 11:03:48PM +0100, Harald Anlauf via Fortran wrote:
>> - if (attr->class_ok)
>> - /* Class container has already been built. */
>> + /* Class container has already been built with same name. */
>> + if (attr->class_ok
>> + && ts->u.derived->components->attr.dimension >= attr->dimension
>> + && ts->u.derived->components->attr.codimension >= attr->codimension
>> + && ts->u.derived->components->attr.class_pointer >= attr->pointer
>> + && ts->u.derived->components->attr.allocatable >= attr->allocatable)
>
> I suppose I'm a bit confused here. dimension, codimension,
> pointer and allocatable are 1-bit bitfields in the attr
> struct. These can have the values 0 and 1, so the above
> conditionals are always true.
thanks for looking into it.
The above part is from the original draft. I thought I could
generate testcases that allow to exercise this part, and found
a new case that is not covered by the patch and still ICEs:
subroutine bar (x)
class(*) :: x
dimension :: x(:)
allocatable :: x
end
:-(
We'll need to revisit the logic...
> The rest of the patch looks reasonable. If Tobias has no
> objections or comments, it's ok to commit once the above
> is explained.
>
Thanks,
Harald
next prev parent reply other threads:[~2023-03-03 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 22:03 Harald Anlauf
2023-03-03 19:57 ` Steve Kargl
2023-03-03 21:17 ` Harald Anlauf [this message]
2023-03-03 21:24 ` Mikael Morin
2023-03-03 22:18 ` Steve Kargl
2023-03-04 13:56 ` Mikael Morin
2023-03-04 16:02 ` [PATCH, v2] " Harald Anlauf
2023-03-04 16:02 ` Harald Anlauf
2023-03-04 16:06 ` Harald Anlauf
2023-03-04 16:06 ` Harald Anlauf
2023-03-04 17:09 ` Mikael Morin
2023-03-04 21:20 ` Harald Anlauf
2023-03-04 22:29 ` Mikael Morin
2023-03-05 20:21 ` [PATCH, v3] " Harald Anlauf
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=7c36addc-00ae-7d75-694b-e47098485e61@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
--cc=tobias@codesourcery.com \
/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: link
Be 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).