public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dorit at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/20501] gcc.dg/vect/vect-93.c fails on ia64-hpux Date: Sun, 20 Mar 2005 12:26:00 -0000 [thread overview] Message-ID: <20050320122620.11041.qmail@sourceware.org> (raw) In-Reply-To: <20050316183640.20501.jsm28@gcc.gnu.org> ------- Additional Comments From dorit at il dot ibm dot com 2005-03-20 12:26 ------- Thanks. This patch should fix the problem (the message "Alignment of access forced using peeling" should not be printed when we're not going to vectorize the loop due to unsupported unaligned access. this patch moves the printing of this message to after the check that the alignment of all accesses is supported): Index: tree-vect-analyze.c =================================================================== RCS file: /cvs/gcc/gcc/gcc/tree-vect-analyze.c,v retrieving revision 2.13 diff -c -3 -p -r2.13 tree-vect-analyze.c *** tree-vect-analyze.c 17 Mar 2005 21:08:06 -0000 2.13 --- tree-vect-analyze.c 20 Mar 2005 12:17:39 -0000 *************** vect_enhance_data_refs_alignment (loop_v *** 1183,1190 **** } DR_MISALIGNMENT (dr0) = 0; - if (vect_print_dump_info (REPORT_ALIGNMENT, LOOP_LOC (loop_vinfo))) - fprintf (vect_dump, "Alignment of access forced using peeling."); } } --- 1183,1188 ---- *************** vect_analyze_data_refs_alignment (loop_v *** 1260,1265 **** --- 1258,1266 ---- && (vect_print_dump_info (REPORT_ALIGNMENT, LOOP_LOC (loop_vinfo)))) fprintf (vect_dump, "Vectorizing an unaligned access."); } + if (LOOP_VINFO_UNALIGNED_DR (loop_vinfo) + && vect_print_dump_info (REPORT_ALIGNMENT, LOOP_LOC (loop_vinfo))) + fprintf (vect_dump, "Alignment of access forced using peeling."); return true; } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20501
next prev parent reply other threads:[~2005-03-20 12:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-16 18:36 [Bug tree-optimization/20501] New: " jsm28 at gcc dot gnu dot org 2005-03-17 20:57 ` [Bug tree-optimization/20501] " dorit at il dot ibm dot com 2005-03-18 1:33 ` jsm28 at gcc dot gnu dot org 2005-03-20 12:26 ` dorit at il dot ibm dot com [this message] 2005-03-22 10:54 ` dorit at il dot ibm dot com 2005-03-23 15:53 ` cvs-commit at gcc dot gnu dot org 2005-03-24 17:15 ` jsm28 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=20050320122620.11041.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).