public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55378] Inconsistant double 387 computation when using osthread under windows Date: Mon, 19 Nov 2012 01:55:00 -0000 [thread overview] Message-ID: <bug-55378-4-f58A6o97ug@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55378-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55378 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|Mingw, cygwin |i?86-*-mingw* | |i?86-*-cygwin-* Component|c |target Host|Windows | Severity|major |normal --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-11-19 01:55:29 UTC --- The difference is 1ulp correct? Maybe there is different rounding modes are selected for the main thread and the spawned threads. Can you see which mode of i387 is used for each? Maybe the spawned threads are using 80bits while the main thread is using 64bits.
next prev parent reply other threads:[~2012-11-19 1:55 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-18 13:00 [Bug c/55378] New: Inconsistant double 387 computation when using osthread philippe.coustaux at gmail dot com 2012-11-18 14:16 ` [Bug c/55378] " philippe.coustaux at gmail dot com 2012-11-19 1:55 ` pinskia at gcc dot gnu.org [this message] 2012-11-19 5:00 ` [Bug target/55378] Inconsistant double 387 computation when using osthread under windows philippe.coustaux at gmail dot com 2012-11-19 5:19 ` philippe.coustaux at gmail dot com 2012-11-19 6:05 ` philippe.coustaux 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-55378-4-f58A6o97ug@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).