public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/39327] New: Incorrect addsub patterns in sse.md Date: Sat, 28 Feb 2009 17:17:00 -0000 [thread overview] Message-ID: <bug-39327-682@http.gcc.gnu.org/bugzilla/> (raw) SSE addsubpX does Adds odd-numbered single-precision floating-point values of the first source operand (second operand) with the corresponding single-precision floating-point values from the second source operand (third operand); stores the result in the odd-numbered values of the destination operand (first operand). Subtracts the even-numbered single-precision floating-point values from the second source operand from the corresponding single-precision floating values in the first source operand; stores the result into the even-numbered values of the destination operand. They are implemented as (define_insn "sse3_addsubv4sf3" [(set (match_operand:V4SF 0 "register_operand" "=x") (vec_merge:V4SF (plus:V4SF (match_operand:V4SF 1 "register_operand" "0") (match_operand:V4SF 2 "nonimmediate_operand" "xm")) (minus:V4SF (match_dup 1) (match_dup 2)) (const_int 5)))] "TARGET_SSE3" "addsubps\t{%2, %0|%0, %2}" [(set_attr "type" "sseadd") (set_attr "prefix_rep" "1") (set_attr "mode" "V4SF")]) We have @item (vec_merge:@var{m} @var{vec1} @var{vec2} @var{items}) This describes a merge operation between two vectors. The result is a vector of mode @var{m}; its elements are selected from either @var{vec1} or @var{vec2}. Which elements are selected is described by @var{items}, which is a bit mask represented by a @code{const_int}; a zero bit indicates the corresponding element in the result vector is taken from @var{vec2} while a set bit indicates it is taken from @var{vec1}. Is item bit reversed? -- Summary: Incorrect addsub patterns in sse.md Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39327
next reply other threads:[~2009-02-28 17:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-28 17:17 hjl dot tools at gmail dot com [this message] 2009-02-28 18:28 ` [Bug target/39327] Incorrect addsub/unpck " hjl dot tools at gmail dot com 2009-02-28 18:34 ` hjl dot tools at gmail dot com 2009-02-28 18:41 ` hjl dot tools at gmail dot com 2009-02-28 22:29 ` hjl at gcc dot gnu dot org 2009-03-12 17:43 ` hjl at gcc dot gnu dot org 2009-03-12 17:50 ` hjl at gcc dot gnu dot org 2009-03-12 22:44 ` hjl dot tools 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-39327-682@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).