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/49826] [4.7 Regression] Symbols are not decorated with attribute stdcall and -mrtd Date: Fri, 30 Dec 2011 17:59:00 -0000 [thread overview] Message-ID: <bug-49826-4-maSKmS0Hlu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49826-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49826 --- Comment #3 from Kai Tietz <ktietz at gcc dot gnu.org> 2011-12-30 17:42:56 UTC --- Hmm, I am not that sure, if this is at all a bug, as linker can handle undecorated stdcall-s quite well as import. I am more curious for what purpose you actual need the @<n> decoration in combination with -mrtd.
next prev parent reply other threads:[~2011-12-30 17:43 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-24 3:20 [Bug target/49826] New: " d.g.gorbachev at gmail dot com 2011-07-24 21:32 ` [Bug target/49826] " pinskia at gcc dot gnu.org 2011-09-14 20:02 ` d.g.gorbachev at gmail dot com 2011-10-10 12:06 ` rguenth at gcc dot gnu.org 2011-10-11 20:13 ` jsm28 at gcc dot gnu.org 2011-12-30 17:59 ` ktietz at gcc dot gnu.org [this message] 2012-01-01 15:34 ` d.g.gorbachev at gmail dot com 2012-03-22 8:41 ` [Bug target/49826] [4.7/4.8 " rguenth at gcc dot gnu.org 2012-06-14 8:10 ` rguenth at gcc dot gnu.org 2012-09-20 10:17 ` jakub at gcc dot gnu.org 2013-01-15 17:54 ` ktietz at gcc dot gnu.org 2013-01-15 23:48 ` d.g.gorbachev at gmail dot com 2013-04-11 7:59 ` [Bug target/49826] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org 2014-06-12 13:45 ` [Bug target/49826] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:30 ` [Bug target/49826] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:22 ` [Bug target/49826] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 19:58 ` [Bug target/49826] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:29 ` jakub at gcc dot gnu.org 2021-05-14 9:46 ` [Bug target/49826] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:05 ` rguenth at gcc dot gnu.org 2022-05-27 9:34 ` [Bug target/49826] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:30 ` jakub at gcc dot gnu.org 2023-07-07 10:29 ` [Bug target/49826] [11/12/13/14 " rguenth 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-49826-4-maSKmS0Hlu@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).