public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: g++ with VLA
Date: Sat, 30 Mar 2024 14:46:14 -0400	[thread overview]
Message-ID: <CAF1jjLvaGr4PAM4sC7kLsufuCDNV6kjbQQv1b0CUSq3XO8B0Ug@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLtCqgNUfeFjJB+QTykWu_i3-9D=OToxX6WMkHugTcX-4g@mail.gmail.com>

On Sat, Mar 30, 2024 at 2:39 PM NightStrike <nightstrike@gmail.com> wrote:
> It looks like clang added support for this in v12.  Maybe it would be
> a good candidate to add support?  I guess I can file the PR and see
> where it lands.

Just to close the loop for the mailing list archive:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114534

      reply	other threads:[~2024-03-30 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30  6:10 NightStrike
2024-03-30  9:05 ` Jonathan Wakely
2024-03-30 18:39   ` NightStrike
2024-03-30 18:46     ` NightStrike [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=CAF1jjLvaGr4PAM4sC7kLsufuCDNV6kjbQQv1b0CUSq3XO8B0Ug@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@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).