public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "irar at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/25881] unsigned int loop indices don't optimize as good as int or __SIZE_TYPE__ for 64bit targets Date: Sun, 29 Jan 2006 10:10:00 -0000 [thread overview] Message-ID: <20060129101056.14305.qmail@sourceware.org> (raw) In-Reply-To: <bug-25881-11859@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from irar at il dot ibm dot com 2006-01-29 10:10 ------- Changing double to float, the scalar evolution analyzer returns access function (float *) ((unsigned int) {0, +, 1}_1 * 4) + (float *) a_12, since it fails in type conversion: (failed conversion: type: unsigned int base: 0 step: estimated_nb_iterations: scev_not_known ) (Without type conversion we get {(float *) a_14, +, 4B}_1). Data-refs analysis fails to analyze the access pattern, therefore the loop does not get vectorized. -- irar at il dot ibm dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian dot pop at cri dot | |ensmp dot fr, irar at il dot | |ibm dot com Last reconfirmed|2006-01-20 20:43:27 |2006-01-29 10:10:55 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25881
next prev parent reply other threads:[~2006-01-29 10:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-20 17:11 [Bug tree-optimization/25881] New: unsigned int loop indices are not accepted by the vectorizer David dot Monniaux at ens dot fr 2006-01-20 17:32 ` [Bug tree-optimization/25881] " pinskia at gcc dot gnu dot org 2006-01-20 20:43 ` [Bug tree-optimization/25881] unsigned int loop indices don't optimize as good as int or __SIZE_TYPE__ for 64bit targets pinskia at gcc dot gnu dot org 2006-01-29 10:10 ` irar at il dot ibm dot com [this message] 2006-10-30 2:46 ` 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=20060129101056.14305.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).