From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Tobias Burnus <tobias@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Use more ARRAY_SIZE.
Date: Mon, 16 May 2022 10:39:58 +0200 [thread overview]
Message-ID: <4110979b-0da8-05e8-ad9f-4e73ef56e933@suse.cz> (raw)
In-Reply-To: <44ed5715-8af0-88a9-8f82-d868df9e33d7@suse.cz>
On 5/11/22 10:17, Martin Liška wrote:
> On 5/9/22 14:03, Richard Biener wrote:
>> On Thu, May 5, 2022 at 4:30 PM Martin Liška <mliska@suse.cz> wrote:
>>>
>>> On 5/5/22 14:58, Iain Buclaw wrote:
>>>> This D front-end change doesn't look right to me, besides the slight
>>>
>>> Hello.
>>>
>>> Sorry, I've re-read the patch and fixed some places where the macro usage
>>> was wrong.
>>>
>>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>>
>> The middle-end parts are OK. I'd say in files where ARRAY_SIZE is already
>> used it's OK to introduce more uses. Otherwise I defer to the more specific
>> maintainers if they like this or not.
>
> All right, CCing the following maintainers for other parts:
>
> - David for JIT and Analyzer
> - Tobias for Fortran part
> - Jason for C-family part
There are not further comments from the remaining C-family part so I'm going
to install the patch.
Martin
>
> Thanks,
> Martin
>
>>
>> Richard.
>>
>>> Martin
>
next prev parent reply other threads:[~2022-05-16 8:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 12:16 Martin Liška
2022-05-05 12:58 ` Iain Buclaw
2022-05-05 14:29 ` Martin Liška
2022-05-09 12:03 ` Richard Biener
2022-05-11 8:17 ` Martin Liška
2022-05-12 9:26 ` Mikael Morin
2022-05-16 8:39 ` Martin Liška [this message]
2022-05-17 19:03 ` [committed] Revert 'Use more ARRAY_SIZE.' for mkoffload (was: [PATCH] Use more ARRAY_SIZE.) Tobias Burnus
2022-05-18 7:40 ` Martin Liška
2022-05-23 7:56 ` [PATCH] Use more ARRAY_SIZE Iain Buclaw
2022-05-23 11:57 ` Martin Liška
2022-05-09 10:21 ` Arnaud Charlet
2022-05-09 10:53 ` Martin Liška
2022-05-09 11:00 ` Arnaud Charlet
2022-05-11 13:52 ` David Malcolm
2022-05-11 19:04 ` Eric Gallager
2022-05-11 19:59 ` David Malcolm
2022-05-12 7:08 ` Richard Biener
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=4110979b-0da8-05e8-ad9f-4e73ef56e933@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--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).