From: Jason Merrill <jason@redhat.com>
To: Javier Martinez <javier.martinez.bugzilla@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v5] c++: extend cold, hot attributes to classes
Date: Tue, 19 Sep 2023 16:58:39 -0400 [thread overview]
Message-ID: <2615d3d2-8f30-4361-80ec-1884f8ca05aa@redhat.com> (raw)
In-Reply-To: <CAL=LcuWfrzQfgnwaxsEvvj=a2XCnjX9wyEsZsWnX=kv0JOgbnQ@mail.gmail.com>
On 9/6/23 06:20, Javier Martinez wrote:
> reminder: ready for commit?
Pushed, thanks!
> - Javier
>
> On Wed 23. Aug 2023 at 15:02, Javier Martinez
> <javier.martinez.bugzilla@gmail.com
> <mailto:javier.martinez.bugzilla@gmail.com>> wrote:
>
> On Tue, Aug 22, 2023 at 7:50 PM Jason Merrill <jason@redhat.com
> <mailto:jason@redhat.com>> wrote:
> > You still need an update to doc/extend.texi for this additional
> use of
> > the attribute. Sorry I didn't think of that before.
>
> I should have caught that too, many thanks.
>
> Also addressed the formatting comments. Patch attached.
>
> Signed-off-by: Javier Martinez <javier.martinez.bugzilla@gmail.com
> <mailto:javier.martinez.bugzilla@gmail.com>>
>
prev parent reply other threads:[~2023-09-19 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 13:02 Javier Martinez
2023-09-06 10:20 ` Javier Martinez
2023-09-19 20:58 ` Jason Merrill [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=2615d3d2-8f30-4361-80ec-1884f8ca05aa@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=javier.martinez.bugzilla@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).