On Wed, 6 May 2020 at 16:33, Marco Elver <el...@google.com> wrote: > > Hello, Jakub, > > On Tue, 28 Apr 2020 at 16:58, Dmitry Vyukov <dvyu...@google.com> wrote: > > > > On Tue, Apr 28, 2020 at 4:55 PM Jakub Jelinek <ja...@redhat.com> wrote: > > > > > > On Tue, Apr 28, 2020 at 04:48:31PM +0200, Dmitry Vyukov wrote: > > > > FWIW this is: > > > > > > > > Acked-by: Dmitry Vyukov <dvuy...@google.com> > > > > > > > > We just landed a similar change to llvm: > > > > https://github.com/llvm/llvm-project/commit/5a2c31116f412c3b6888be361137efd705e05814 > > > > > > > > Do you have any objections? > > > > > > I don't have objections or anything right now, we are just trying to > > > finalize GCC 10 and once it branches, patches like this can be > > > reviewed/committed for GCC11. > > > > Thanks for clarification! > > Then we will just wait. > > Just saw the announcement that GCC11 is in development stage 1 [1]. In > case it is still too early, do let us know what time window we shall > follow up. > > Would it be useful to rebase and resend the patch?
So, it's starting to look like we're really going to need this sooner than later. Given the feature is guarded behind a flag, and otherwise does not affect anything else, would it be possible to take this for GCC11? What do we need to do to make this happen? Thanks, -- Marco > [1] https://gcc.gnu.org/pipermail/gcc/2020-April/000505.html
