public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55940] Incorrect code for accessing parameters with 32-bit Intel hosts Date: Tue, 15 Jan 2013 15:22:00 -0000 [thread overview] Message-ID: <bug-55940-4-RlCDAMoOme@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55940-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55940 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-15 15:22:14 UTC --- You haven't provided the preprocessed testcase, so it is hard to guess, but generally, if you have say a static function and call it also from assembly, you need __attribute__((used)) to prevent the compiler from using different calling conventions. Otherwise, if the compiler can see all possible callers (inline asm doesn't count, then you have to use the used attribute), it can decide not to emit the function at all, or use whatever calling convention it thinks are best for the function.
next prev parent reply other threads:[~2013-01-15 15:22 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-11 11:17 [Bug target/55940] New: " fm3 at os dot inf.tu-dresden.de 2013-01-11 11:23 ` [Bug target/55940] " rguenth at gcc dot gnu.org 2013-01-11 11:27 ` rguenth at gcc dot gnu.org 2013-01-11 11:36 ` rguenth at gcc dot gnu.org 2013-01-15 13:53 ` fm3 at os dot inf.tu-dresden.de 2013-01-15 15:04 ` fm3 at os dot inf.tu-dresden.de 2013-01-15 15:22 ` jakub at gcc dot gnu.org [this message] 2013-01-15 15:38 ` fm3 at os dot inf.tu-dresden.de 2013-01-15 16:55 ` fm3 at os dot inf.tu-dresden.de 2013-01-15 16:56 ` fm3 at os dot inf.tu-dresden.de 2013-01-15 16:58 ` fm3 at os dot inf.tu-dresden.de 2013-01-15 17:46 ` [Bug target/55940] [4.7/4.8 Regression] " jakub at gcc dot gnu.org 2013-01-15 18:29 ` jakub at gcc dot gnu.org 2013-01-15 22:59 ` jakub at gcc dot gnu.org 2013-01-16 8:00 ` [Bug target/55940] [4.7 " jakub at gcc dot gnu.org 2013-01-16 9:01 ` fm3 at os dot inf.tu-dresden.de 2013-01-16 9:16 ` jakub at gcc dot gnu.org 2013-02-01 14:10 ` jakub at gcc dot gnu.org 2013-02-01 14:31 ` jakub 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-55940-4-RlCDAMoOme@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).