public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ttimo at valvesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95883] Attributes on lambdas appear to be parsed in the wrong place
Date: Mon, 29 Jun 2020 21:15:44 +0000	[thread overview]
Message-ID: <bug-95883-4-Y74SUUWJRz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95883-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95883

--- Comment #4 from Timothee Besset <ttimo at valvesoftware dot com> ---
We are in the same situation; we are assessing a move to a newer gcc but we
need to maintain compatibility with older gcc, at least for the time being. We
would like to avoid having to use macros for all of this.

  parent reply	other threads:[~2020-06-29 21:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 19:51 [Bug c++/95883] New: " drewb at valvesoftware dot com
2020-06-25 13:09 ` [Bug c++/95883] " ttimo at valvesoftware dot com
2020-06-25 23:32 ` ttimo at valvesoftware dot com
2020-06-29 21:12 ` patrick.a.moran at gmail dot com
2020-06-29 21:15 ` ttimo at valvesoftware dot com [this message]
2021-02-26  4:15 ` jason at gcc dot gnu.org

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=bug-95883-4-Y74SUUWJRz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).