public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sourceforge.com-20020529 at reg dot pizzolato.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/48730] New: static function scope not honored by -fms-extensions Date: Fri, 22 Apr 2011 16:04:00 -0000 [thread overview] Message-ID: <bug-48730-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48730 Summary: static function scope not honored by -fms-extensions Product: gcc Version: 4.5.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: sourceforge.com-20020529@reg.pizzolato.net gcc running on Windows via MinGW. Microsoft describes extensions to C at http://msdn.microsoft.com/en-us/library/34h23df8(v=vs.80).aspx The case I encountered relates to the following: extern int clip(); static int clip() {} which gcc fails to compile: clip.c:2:12: error: static declaration of 'clip' follows non-static declaration clip.c:1:12: note: previous declaration of 'clip' was here The original code which encountered this error wasn't this simple. The 'extern int function();' was buried in some deeply nested layers of system include files, and the locally scoped function had a name which was identical to the one defined in the include file. The code compiles cleanly with Microsoft's compilers but fails with the above error when compiled with gcc. gcc behaves the same, in this case, without regard to the presense of the '-fms-extensions' command option. It would seem appropriate that this behavior like the microsoft compilers should be part of the functionality of '-fms-extensions'.
next reply other threads:[~2011-04-22 16:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-22 16:04 sourceforge.com-20020529 at reg dot pizzolato.net [this message] 2011-04-23 9:13 ` [Bug c/48730] " rguenth at gcc dot gnu.org 2021-09-17 7:25 ` 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-48730-4@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: 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).