public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Matthias Klose <doko@klose.in-berlin.de> To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org Subject: c/6904: GCC attribute syntax Date: Sat, 01 Jun 2002 15:46:00 -0000 [thread overview] Message-ID: <E17EHF4-0007BQ-00@gate.local> (raw) >Number: 6904 >Category: c >Synopsis: GCC attribute syntax >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Sat Jun 01 15:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Ian Jackson <ian@davenant.greenend.org.uk> >Release: 3.1 (Debian) (Debian unstable) >Organization: The Debian Project >Environment: System: Debian GNU/Linux (unstable) Architecture: i686 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii gcc-3.1 3.1-2 The GNU C compiler. ii binutils 2.12.90.0.7-1 The GNU assembler, linker and binary utiliti ii libc6 2.2.5-6 GNU C Library: Shared libraries and Timezone host: i386-linux configured with: /mnt/data/gcc-3.1/gcc-3.1-3.1ds2/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=$\(prefix\)/share/man --infodir=$\(prefix\)/share/info --with-gxx-include-dir=$\(prefix\)/include/g++-v3-3.1 --enable-shared --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --enable-clocale=gnu --enable-threads=posix --enable-java-gc=boehm --enable-objc-gc i386-linux >Description: [ Reported to the Debian BTS as report #12253. Please CC 12253@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/12253 ] [ The documentation has been updated: http://gcc.gnu.org/ml/gcc-patches/2001-01/msg01683.html The "obvious" syntax isn't accepted. ] The function __attribute__((...)) extension in GCC is very useful. However, it has something of a niggle in its use. If the relevant declaration of a function is also its definition then you cannot use __attribute__ in the way suggested by the examples in the GCC manual; GCC rejects the `obvious' usage with a syntax error. The manual does not give a formal definition of where function attributes may appear, but the examples are all like int square (int) __attribute__ ((const)); suggesting that in a definition it should appear between the argument list and the opening brace. However, GCC does not accept that syntax. Experimenting shows that it _does_ accept a syntax where the attributes appear immediately before the function name (at least for functions with return values not of a pointer type). I think it would be useful to accept the `obvious' syntax (e.g., u.c in my transcript below). I also think the syntax which is accepted should be specified; in particular, the locations where the __attribute__ may appear should be specified. Thanks, Ian. -davenant:~/junk> cat t.c static void f(void) __attribute__((noreturn)); static void f(void) { } -davenant:~/junk> gcc -Wall -O3 -c t.c t.c: In function `f': t.c:2: warning: `noreturn' function does return -davenant:~/junk> cat u.c static void f(void) __attribute__((noreturn)) { } -davenant:~/junk> gcc -Wall -O3 -c u.c u.c:1: parse error before `{' u.c:1: warning: `f' declared `static' but never defined -davenant:~/junk> cat v.c static void __attribute__((noreturn)) f(void) { } -davenant:~/junk> gcc -Wall -O3 -c v.c v.c: In function `f': v.c:1: warning: `noreturn' function does return -davenant:~/junk> >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-01 22:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-01 15:46 Matthias Klose [this message] 2002-06-02 0:13 rth
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=E17EHF4-0007BQ-00@gate.local \ --to=doko@klose.in-berlin.de \ --cc=12253@bugs.debian.org \ --cc=debian-gcc@lists.debian.org \ --cc=gcc-gnats@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: linkBe 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).