From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>,
"Richard Biener" <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH 1/3] vec: add exact argument for various grow functions.
Date: Wed, 26 Aug 2020 14:59:50 -0600 [thread overview]
Message-ID: <f47f957510957ac449d4244204d0f4f5d44fc47a.camel@redhat.com> (raw)
In-Reply-To: <f15aa1e9-38ca-aca2-ef15-a6602159fcb9@suse.cz>
On Tue, 2020-08-11 at 13:36 +0200, Martin Liška wrote:
> Hello.
>
> All right, I did it in 3 steps:
> 1) - new exact argument is added (no default value) - I tested the on x86_64-linux-gnu
> and I build all cross targets.
> 2) set default value of exact = false
> 3) change places which calculate its own growth to use the default argument
>
> I would like to install first 1) and then wait some time before the rest is installed.
>
> Thoughts?
Given this is how Richi wanted the series to play out. #1 is fine with me as is
the plan for the kit as a whole.
Jeff
>
next prev parent reply other threads:[~2020-08-26 20:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 12:22 [PATCH] Use vec::reserve before vec_safe_grow_cleared is called Martin Liška
2020-07-27 7:11 ` Richard Biener
2020-07-27 7:14 ` Martin Liška
2020-07-27 9:51 ` Jan Hubicka
2020-07-27 10:29 ` Martin Liška
2020-07-27 10:48 ` Jan Hubicka
2020-07-27 11:00 ` Martin Liška
2020-07-27 11:03 ` Jan Hubicka
2020-07-27 11:22 ` Martin Liška
2020-07-27 12:49 ` Andreas Schwab
2020-07-27 12:51 ` Richard Biener
2020-07-27 12:54 ` Martin Liška
2020-07-27 12:58 ` Richard Biener
2020-07-27 11:07 ` Richard Biener
2020-07-27 11:11 ` Jan Hubicka
2020-07-27 11:24 ` Martin Liška
2020-07-27 11:31 ` Richard Biener
2020-07-28 10:23 ` [PATCH] Use exact=false for vec_safe_grow{,_cleared} functions Martin Liška
2020-07-29 13:47 ` Richard Biener
2020-07-30 13:22 ` Martin Liška
2020-08-03 13:47 ` Richard Biener
2020-08-11 11:36 ` [PATCH 1/3] vec: add exact argument for various grow functions Martin Liška
2020-08-11 11:37 ` [PATCH 2/3] vec: default exact = false in " Martin Liška
2020-08-26 21:00 ` Jeff Law
2020-08-11 11:37 ` [PATCH 3/3] vec: use inexact growth where possible Martin Liška
2020-08-26 21:02 ` Jeff Law
2020-08-27 8:54 ` Richard Biener
2020-09-01 11:25 ` Martin Liška
2020-09-01 13:00 ` Richard Biener
2020-08-11 14:58 ` [PATCH 1/3] vec: add exact argument for various grow functions Martin Sebor
2020-08-12 12:28 ` Martin Liška
2020-08-13 0:18 ` Martin Sebor
2020-08-26 13:54 ` Martin Liška
2020-08-27 23:29 ` Martin Sebor
2020-08-28 6:49 ` Martin Liška
2020-08-28 14:35 ` Martin Sebor
2020-08-26 20:59 ` Jeff Law [this message]
2020-08-28 14:24 ` Andrew Stubbs
2020-08-28 14:26 ` Martin Liška
2020-08-28 14:44 ` Andrew Stubbs
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=f47f957510957ac449d4244204d0f4f5d44fc47a.camel@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mliska@suse.cz \
--cc=richard.guenther@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).