public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/101265] C2X [[maybe_unused]] ignored when placed after array declaration
Date: Wed, 30 Jun 2021 22:59:33 +0000	[thread overview]
Message-ID: <bug-101265-4-Di1UroFMja@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101265-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 30 Jun 2021, gcc at alanwu dot email via Gcc-bugs wrote:

> >     [[attr1]] int [[attr2]] a[10] [[attr3]], b [[attr4]];
> > attr1 appertains to the variable declarations a and b, attr2
> > appertains to the type int, attr3 appertains to the variable
> > declaration a, and attr4 appertains to the variable declaration b.

That looks like an error in introductory text describing that proposal 
(not text that was proposed for addition to the standard itself).  I at 
least mainly concentrate on the proposed changes to the standard text when 
reviewing the details of C standards proposals; mistakes of detail outside 
those changes aren't really important.  The current working draft is 
N2596, which has plenty of attributes-related changes that postdate the 
original proposal for attributes support; you should search for the word 
"appertain" there and disregard the older proposal.

  parent reply	other threads:[~2021-06-30 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 20:09 [Bug c/101265] New: " gcc at alanwu dot email
2021-06-30 16:54 ` [Bug c/101265] " joseph at codesourcery dot com
2021-06-30 22:17 ` gcc at alanwu dot email
2021-06-30 22:59 ` joseph at codesourcery dot com [this message]
2021-07-01 13:21 ` gcc at alanwu dot email

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-101265-4-Di1UroFMja@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).