public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/24903] dotprod should use conj? Date: Thu, 16 Feb 2006 07:52:00 -0000 [thread overview] Message-ID: <20060216075228.24811.qmail@sourceware.org> (raw) In-Reply-To: <bug-24903-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from fxcoudert at gcc dot gnu dot org 2006-02-16 07:52 ------- Subject: Bug 24903 Author: fxcoudert Date: Thu Feb 16 07:52:22 2006 New Revision: 111131 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=111131 Log: PR libfortran/24903 * m4/dotprodc.m4: Use __builtin_conj instead of assigning real and imaginary parts separately. * generated/dotprod_c4.c: Regenerated. * generated/dotprod_c8.c: Regenerated. * generated/dotprod_c10.c: Regenerated. * generated/dotprod_c16.c: Regenerated. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/generated/dotprod_c10.c trunk/libgfortran/generated/dotprod_c16.c trunk/libgfortran/generated/dotprod_c4.c trunk/libgfortran/generated/dotprod_c8.c trunk/libgfortran/m4/dotprodc.m4 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24903
next prev parent reply other threads:[~2006-02-16 7:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-16 19:02 [Bug libfortran/24903] New: " pinskia at gcc dot gnu dot org 2005-11-20 0:40 ` [Bug libfortran/24903] " pinskia at gcc dot gnu dot org 2005-11-21 9:11 ` fxcoudert at gcc dot gnu dot org 2005-11-21 22:53 ` pinskia at gcc dot gnu dot org 2006-02-06 22:16 ` fxcoudert at gcc dot gnu dot org 2006-02-16 7:52 ` fxcoudert at gcc dot gnu dot org [this message] 2006-02-16 7:53 ` [Bug libfortran/24903] [4.1 only] dotprod should use __builtin_conj fxcoudert at gcc dot gnu dot org 2006-03-04 8:53 ` fxcoudert at gcc dot gnu dot org 2006-03-04 8:55 ` [Bug libfortran/24903] " fxcoudert 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=20060216075228.24811.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).