From: Tom de Vries <Tom_deVries@mentor.com>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
Tobias Burnus <burnus@net-b.de>
Cc: gcc patches FOR <gcc-patches@gcc.gnu.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: [4.8, Fortran, Patch] PR 48820 - Support TYPE(*) of TS29113
Date: Wed, 03 Dec 2014 00:21:00 -0000 [thread overview]
Message-ID: <547E575A.1060808@mentor.com> (raw)
In-Reply-To: <CAGkQGiKmNMfQ9gMJvo=WC+LFcFEkA_qVo3pxTBMitYnUDr41Eg@mail.gmail.com>
On 03/03/12 08:41, Paul Richard Thomas wrote:
> Dear Tobias,
>
> This is certainly OK for 4.8.
>
> I have a couple of remarks:
> (i) The DTYPE_TYPE_MASK is 0x38 so that we saturated it a long time
> since! At the moment it does not cause any problems because of the
> extremely limited use of the dtype 'type'.
Hi,
AFAIU, you're saying here that since there are very few uses of the type part of
dtype, it's not a problem.
But at the moment, BT_ASSUMED with value 11 bleeds into the size part of dtype.
In gfc_get_dtype_rank_type, we just set the type directly without applying the mask:
...
i = rank | (n << GFC_DTYPE_TYPE_SHIFT);
...
In fact, the mask seems completely unused.
> Whilst the array
> descriptor revamp will eliminate such worries, we should be mindful of
> this; and
I think that if we have a mask that we're not respecting, we need to clearly
document at the definiton how that's done and why that's not a problem. And
ideally, add some asserts to detect when we break that allowed usage pattern.
Thanks,
- Tom
prev parent reply other threads:[~2014-12-03 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 11:28 Tobias Burnus
2012-03-03 7:41 ` Paul Richard Thomas
2012-03-03 10:13 ` Tobias Burnus
2012-03-03 14:17 ` Tobias Burnus
2012-03-03 18:56 ` Tobias Burnus
2014-12-03 0:21 ` Tom de Vries [this message]
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=547E575A.1060808@mentor.com \
--to=tom_devries@mentor.com \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.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).