public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fm3 at os dot inf.tu-dresden.de" <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 16:58:00 -0000 [thread overview] Message-ID: <bug-55940-4-kulbrOle3U@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 --- Comment #10 from Frank Mehnert <fm3 at os dot inf.tu-dresden.de> 2013-01-15 16:57:48 UTC --- And regarding your comment, Jakub, in this case it's not a question of not emitting the code of a function or not. The function code is emitted and the code is definitely wrong. EDI was not initialized before it was used.
next prev parent reply other threads:[~2013-01-15 16:58 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 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 [this message] 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-kulbrOle3U@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).