public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63326] whether a #pragma is a statement depends on the type of pragma
Date: Fri, 27 Mar 2020 18:47:47 +0000	[thread overview]
Message-ID: <bug-63326-4-3evgvVRuiB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63326-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #28 from Romain Geissler <romain.geissler at amadeus dot com> ---
Hi David,

Do you have plans to submit this patch for review when stage 1 of gcc 11 opens
?

Cheers,
Romain

  parent reply	other threads:[~2020-03-27 18:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  6:37 [Bug c/63326] New: pragma GCC causes wrong code generation dietmar.schindler@manroland-web.com
2014-09-22  6:41 ` [Bug c/63326] " pinskia at gcc dot gnu.org
2014-09-24 11:46 ` dietmar.schindler@manroland-web.com
2014-09-24 14:36 ` manu at gcc dot gnu.org
2014-09-24 15:41 ` [Bug c/63326] whether a #pragma is a statement depends on the type of pragma pinskia at gcc dot gnu.org
2014-10-21 23:20 ` pinskia at gcc dot gnu.org
2014-10-22  8:37 ` rguenth at gcc dot gnu.org
2014-10-22  9:12 ` jakub at gcc dot gnu.org
2014-10-22 12:50 ` manu at gcc dot gnu.org
2014-10-22 14:08 ` q.gcc@rsn-tech.co.uk
2014-10-22 14:11 ` manu at gcc dot gnu.org
2020-03-27 18:40 ` pinskia at gcc dot gnu.org
2020-03-27 18:47 ` romain.geissler at amadeus dot com [this message]
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-07-23  6:51 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-07-20 19:40 ` msebor at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07  7:27 ` rguenth at gcc dot gnu.org
2023-10-10 12:13 ` pinskia at gcc dot gnu.org
2024-01-24 17:27 ` pinskia 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-63326-4-3evgvVRuiB@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).