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/6902: stdcall function attribute doesn't work any longer Date: Sat, 01 Jun 2002 15:06:00 -0000 [thread overview] Message-ID: <E17EGsp-00076A-00@gate.local> (raw) >Number: 6902 >Category: c >Synopsis: stdcall function attribute doesn't work any longer >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Jun 01 15:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: markus.oberhumer@jk.uni-linz.ac.at >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 #43119. Please CC 43119@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/43119 ] Markus F.X.J. Oberhumer writes: > Package: gcc > Version: 2.95.1-0pre1 > > gcc exits with a "conflicting types" error when > compiling the code below. > > Markus > > int foo1(void) __attribute__((stdcall)); > int foo1(void) > { > return 1; > } > > int foo2(void) __attribute__((__stdcall__)); > int foo2(void) > { > return 2; > } In the documentation ("Declaring Attributes of Functions"), I find: "The keyword `__attribute__' allows you to specify special attributes when making a declaration." However if the attribute is repeated at the definition of the function, I get an parse error (according to the documentation): int foo1(void) __attribute__((stdcall)); int foo1(void) __attribute__((stdcall)) { return 1; } bug-43119-2.c:3: parse error before `{' When using the now undocumented way of moving the attribute before the function name, neither the parse error nor the type conflict occur: int foo1(void) __attribute__((stdcall)); int __attribute__((stdcall)) foo1(void) { return 1; } >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-01 22:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-01 15:06 Matthias Klose [this message] 2002-06-02 0:09 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=E17EGsp-00076A-00@gate.local \ --to=doko@klose.in-berlin.de \ --cc=43119@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).