public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jbeulich at novell dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17603] [4.0 Regression] cpowf and cpowl give wrong results Date: Thu, 16 Dec 2004 12:59:00 -0000 [thread overview] Message-ID: <20041216125925.21372.qmail@sourceware.org> (raw) In-Reply-To: <20040922093853.17603.pcarlini@suse.de> ------- Additional Comments From jbeulich at novell dot com 2004-12-16 12:59 ------- This happens when the ABI is (was) imprecise. Earlier versions did not special case long double complex, but the current version does. Hence I have a patch ready that partly reverses the original change (actually, implements the original behavior for this type in a form slightly closer matching the ABI definition); expecting to submit this later today or tomorrow (currently building/testing). As to the same(?) problem observed with float complex: I doubt the mentioned patch causes this, since behavior for that type wasn't modified by it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17603
next prev parent reply other threads:[~2004-12-16 12:59 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-22 9:38 [Bug middle-end/17603] New: Cpowf and cpowl builtins broken pcarlini at suse dot de 2004-09-22 12:21 ` [Bug middle-end/17603] [4.0 Regression] " pinskia at gcc dot gnu dot org 2004-09-22 12:30 ` pcarlini at suse dot de 2004-09-22 12:39 ` pinskia at gcc dot gnu dot org 2004-09-22 12:44 ` pcarlini at suse dot de 2004-09-22 12:57 ` pinskia at gcc dot gnu dot org 2004-09-28 3:06 ` pinskia at gcc dot gnu dot org 2004-09-28 8:07 ` pcarlini at suse dot de 2004-09-28 15:44 ` [Bug middle-end/17603] [4.0 Regression] cpowf and cpowl give wrong results pcarlini at suse dot de 2004-11-02 3:07 ` coyote at coyotegulch dot com 2004-11-02 7:39 ` steven at gcc dot gnu dot org 2004-12-05 20:43 ` [Bug target/17603] " pinskia at gcc dot gnu dot org 2004-12-05 21:03 ` pcarlini at suse dot de 2004-12-05 21:24 ` roger at eyesopen dot com 2004-12-15 22:07 ` steven at gcc dot gnu dot org 2004-12-15 23:51 ` pcarlini at suse dot de 2004-12-16 1:05 ` steven at gcc dot gnu dot org 2004-12-16 1:09 ` steven at gcc dot gnu dot org 2004-12-16 1:14 ` pinskia at gcc dot gnu dot org 2004-12-16 12:59 ` jbeulich at novell dot com [this message] 2004-12-16 15:46 ` jbeulich at novell dot com 2004-12-16 16:33 ` pinskia at gcc dot gnu dot org 2004-12-17 8:54 ` cvs-commit at gcc dot gnu dot org 2004-12-17 12:23 ` pinskia at gcc dot gnu dot 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=20041216125925.21372.qmail@sourceware.org \ --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).