public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55268] gcc4.8 mingw-w64 wrong stdcall import symbols generated after rev 193204 Date: Wed, 14 Nov 2012 12:28:00 -0000 [thread overview] Message-ID: <bug-55268-4-zCkJ5V9YwI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55268-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55268 Kai Tietz <ktietz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-11-14 CC| |ktietz at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #2 from Kai Tietz <ktietz at gcc dot gnu.org> 2012-11-14 12:28:22 UTC --- I have the following patch which should solve this issue: Index: i386.c =================================================================== --- i386.c (Revision 193485) +++ i386.c (Arbeitskopie) @@ -28805,7 +28805,10 @@ /* For function version, add the target suffix to the assembler name. */ if (TREE_CODE (decl) == FUNCTION_DECL && DECL_FUNCTION_VERSIONED (decl)) - return ix86_mangle_function_version_assembler_name (decl, id); + id = ix86_mangle_function_version_assembler_name (decl, id); +#ifdef TARGET_MANGLE_DECL_ASSEMBLER_NAME + id = TARGET_MANGLE_DECL_ASSEMBLER_NAME (decl, id); +#endif return id; }
next prev parent reply other threads:[~2012-11-14 12:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-11 5:29 [Bug target/55268] New: gcc4.8 mingw-w64 Wrong " squallatf at gmail dot com 2012-11-11 11:06 ` [Bug target/55268] gcc4.8 mingw-w64 wrong " squallatf at gmail dot com 2012-11-14 12:28 ` ktietz at gcc dot gnu.org [this message] 2012-11-14 12:36 ` ktietz at gcc dot gnu.org 2012-11-20 16:17 ` ktietz at gcc dot gnu.org 2012-11-20 18:21 ` ktietz 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-55268-4-zCkJ5V9YwI@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).