public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: implement vector sections in DATA statements [PR49588]
Date: Tue, 22 Aug 2023 20:45:15 +0200	[thread overview]
Message-ID: <32a1acd3-11c6-4692-a940-87f343c862f4@gmx.de> (raw)
In-Reply-To: <CAGkQGiK3Vk=Zjxhie1oOQS8kv5OEam_Rj0v0k4-p-6WVHO4tbg@mail.gmail.com>

Hi Paul,

Am 22.08.23 um 08:32 schrieb Paul Richard Thomas via Gcc-patches:
> Hi Harald,
>
> It all looks good to me and does indeed make the code clearer. OK for trunk.
>
> Thanks for the patch.

thanks for the review!

> I was shocked to find that there are 217 older bugs than 49588. Does
> anybody test older bugs to check if any of them have been fixed?

I am not aware of this being done systematically.

At the same time, we have over 100 PRs marked as regression,
with a few being fixed on mainline but not backported (or
undecided whether to backport).  Fixing and/or closing them
might be low-hanging fruits.

There are also far more than 100 TODOs in gcc/fortran/*.cc ...

And with the usual PRs, there's enough work left for all kinds
of contributions.

Cheers,
Harald

> Paul
>
> On Mon, 21 Aug 2023 at 20:48, Harald Anlauf via Fortran
> <fortran@gcc.gnu.org> wrote:
>>
>> Dear all,
>>
>> the attached patch implements vector sections in DATA statements.
>>
>> The implementation is simpler than the size of the patch suggests,
>> as part of changes try to clean up the existing code to make it
>> easier to understand, as ordinary sections (start:end:stride)
>> and vector sections may actually share some common code.
>>
>> The basisc idea of the implementation is that one needs a
>> temporary vector that keeps track of the offsets into the
>> array constructors for the indices in the array reference
>> that are vectors.
>>
>> Regtested on x86_64-pc-linux-gnu.  OK for mainline?
>>
>> Thanks,
>> Harald
>>
>


      reply	other threads:[~2023-08-22 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 19:48 Harald Anlauf
2023-08-22  6:32 ` Paul Richard Thomas
2023-08-22 18:45   ` Harald Anlauf [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=32a1acd3-11c6-4692-a940-87f343c862f4@gmx.de \
    --to=anlauf@gmx.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).