From: Jeff Law <jeffreyalaw@gmail.com>
To: Costas Argyris <costas.argyris@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gcc-ar: Remove code duplication.
Date: Sat, 17 Jun 2023 14:39:01 -0600 [thread overview]
Message-ID: <9e898232-3ba8-7595-f5a3-94a794531ca6@gmail.com> (raw)
In-Reply-To: <CAHyHGCnYjq-C1-hm022qLkqSXfDJ5dUPBgyyJb-12WQ105Zxpg@mail.gmail.com>
On 6/15/23 06:10, Costas Argyris via Gcc-patches wrote:
> From c3f3b2fd53291805b5d0be19df6d1a348c5889ec Mon Sep 17 00:00:00 2001
> From: Costas Argyris<costas.argyris@gmail.com>
> Date: Thu, 15 Jun 2023 12:37:35 +0100
> Subject: [PATCH] gcc-ar: Remove code duplication.
>
> Preparatory refactoring that simplifies by eliminating
> some duplicated code, before trying to fix 77576.
> I believe this stands on its own regardless of the PR.
> It also saves a nargv element when we have a plugin and
> three when not.
Thanks. I've commited this to the trunk after adding a suitable
ChangeLog entry.
jeff
prev parent reply other threads:[~2023-06-17 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:10 Costas Argyris
2023-06-17 20:39 ` Jeff Law [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=9e898232-3ba8-7595-f5a3-94a794531ca6@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=costas.argyris@gmail.com \
--cc=gcc-patches@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: 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).