public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59405] Incorrect FP<->MMX transition during call/ret Date: Fri, 06 Dec 2013 17:16:00 -0000 [thread overview] Message-ID: <bug-59405-4-04d6yInsAV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59405-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59405 --- Comment #9 from uros at gcc dot gnu.org --- Author: uros Date: Fri Dec 6 17:16:52 2013 New Revision: 205753 URL: http://gcc.gnu.org/viewcvs?rev=205753&root=gcc&view=rev Log: PR target/59405 * config/i386/i386.c (type_natural_mode): Properly handle size 8 for !TARGET_64BIT. testsuite/ChangeLog: PR target/59405 * gcc.target/i386/pr59405.c: New test. Added: trunk/gcc/testsuite/gcc.target/i386/pr59405.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2013-12-06 17:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-06 11:05 [Bug target/59405] New: " kirill.yukhin at intel dot com 2013-12-06 11:17 ` [Bug target/59405] " ubizjak at gmail dot com 2013-12-06 11:18 ` kirill.yukhin at intel dot com 2013-12-06 11:19 ` kirill.yukhin at intel dot com 2013-12-06 11:25 ` ubizjak at gmail dot com 2013-12-06 11:47 ` kirill.yukhin at intel dot com 2013-12-06 12:00 ` hjl.tools at gmail dot com 2013-12-06 12:30 ` ubizjak at gmail dot com 2013-12-06 17:16 ` uros at gcc dot gnu.org [this message] 2013-12-06 17:27 ` ubizjak at gmail dot com 2013-12-08 14:20 ` uros at gcc dot gnu.org 2013-12-08 14:22 ` ubizjak at gmail dot com
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-59405-4-04d6yInsAV@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).