public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/46391] false dependencies are computed after vectorization (#2) Date: Tue, 09 Nov 2010 13:19:00 -0000 [thread overview] Message-ID: <bug-46391-4-iAV888QqlQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46391-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46391 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-11-09 13:18:47 UTC --- On x86_64 restrict information is there (-fdump-tree-optimized-alias): <bb 5>: # PT = nonlocal { PARM_RESTRICT.0 } (restr) vect_p.27_71 = c_8(D) + prolog_loop_niters.16_27; # PT = nonlocal { PARM_RESTRICT.1 } (restr) vect_p.32_75 = d_5(D) + prolog_loop_niters.16_27; <bb 6>: # ivtmp.52_46 = PHI <ivtmp.52_31(6), 0(5)> # ivtmp.55_47 = PHI <ivtmp.55_33(6), 0(5)> vect_var_.28_74 = MEM[base: vect_p.27_71, index: ivtmp.55_47, offset: 0B]; MEM[base: vect_p.32_75, index: ivtmp.55_47, offset: 0B] = vect_var_.28_74; ivtmp.52_31 = ivtmp.52_46 + 1; ivtmp.55_33 = ivtmp.55_47 + 16; if (ivtmp.52_31 < bnd.20_49) goto <bb 6>; else goto <bb 7>;
next prev parent reply other threads:[~2010-11-09 13:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-09 12:35 [Bug rtl-optimization/46391] New: " roy.1rosen at gmail dot com 2010-11-09 13:19 ` rguenth at gcc dot gnu.org [this message] 2010-11-09 13:48 ` [Bug rtl-optimization/46391] " roy.1rosen at gmail dot com 2010-11-11 8:04 ` roy.1rosen at gmail dot com 2021-08-16 4:29 ` pinskia at gcc dot gnu.org 2021-09-08 11:04 ` rguenth at gcc dot gnu.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=bug-46391-4-iAV888QqlQ@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).