public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kirill.yukhin at intel dot com" <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 11:19:00 -0000 [thread overview] Message-ID: <bug-59405-4-jXxaWkBJ8u@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 #3 from Yukhin Kirill <kirill.yukhin at intel dot com> --- (In reply to Uroš Bizjak from comment #1) > There is no testcase attached, but you need to *manually* insert _mm_empty > (== emms) to switch from MMX to x87 state. > > The compiler does not automatically insert emms for you. Well, then problem is different, test as simple as empty call. I doubt we should emit wrong code here. >From gcc-bugs-return-436820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:23:18 2013 Return-Path: <gcc-bugs-return-436820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 17646 invoked by alias); 6 Dec 2013 11:23:18 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 17597 invoked by uid 48); 6 Dec 2013 11:23:14 -0000 From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59188] [4.9 Regression] lib64/libtsan.so: undefined reference to `sigsetjmp' Date: Fri, 06 Dec 2013 11:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Joost.VandeVondele at mat dot ethz.ch X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-59188-4-yVB5zLkVIG@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59188-4@http.gcc.gnu.org/bugzilla/> References: <bug-59188-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg00475.txt.bz2 Content-length: 583 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY188 Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #12 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> --- (In reply to Kostya Serebryany from comment #11) > planing next merge from llvm to gcc in ~1 week. Fixed in current trunk. Thanks!
next prev parent reply other threads:[~2013-12-06 11:19 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 [this message] 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 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-jXxaWkBJ8u@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).