public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bviyer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59691] cilk-plus run failures on non-sse processors
Date: Mon, 10 Feb 2014 16:57:00 -0000 [thread overview]
Message-ID: <bug-59691-4-gbnx71A482@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59691-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59691
--- Comment #10 from bviyer at gcc dot gnu.org ---
Author: bviyer
Date: Mon Feb 10 16:56:54 2014
New Revision: 207664
URL: http://gcc.gnu.org/viewcvs?rev=207664&root=gcc&view=rev
Log:
Fix for PR target/59691.
+2014-02-10 Balaji V. Iyer <balaji.v.iyer@intel.com>
+
+ PR target/59691
+ * runtime/config/x86/os-unix-sysdep.c (__builtin_cpu_supports): New
+ function.
+ (restore_x86_fp_state): Added a check if the cpu supports the
+ instruction before emitting it.
+ (sysdep_save_fp_ctrl_state): Likewise.
+
Modified:
trunk/libcilkrts/ChangeLog
trunk/libcilkrts/runtime/config/x86/os-unix-sysdep.c
next prev parent reply other threads:[~2014-02-10 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 23:25 [Bug other/59691] New: cilk-plus failure on PENTIUM2 bernd.edlinger at hotmail dot de
2014-01-06 0:06 ` [Bug target/59691] cilk-plus run failures on non-sse processors pinskia at gcc dot gnu.org
2014-01-22 17:37 ` bviyer at gmail dot com
2014-01-22 17:45 ` pinskia at gcc dot gnu.org
2014-01-22 17:53 ` law at redhat dot com
2014-01-23 18:06 ` bviyer at gmail dot com
2014-01-23 18:08 ` bviyer at gmail dot com
2014-01-25 8:13 ` bernd.edlinger at hotmail dot de
2014-01-25 13:30 ` hjl.tools at gmail dot com
2014-01-25 15:20 ` bviyer at gmail dot com
2014-02-10 16:57 ` bviyer at gcc dot gnu.org [this message]
2014-02-10 17:44 ` law at redhat 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-59691-4-gbnx71A482@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: link
Be 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).