public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65355] [4.8/4.9/5 Regression] vectorizer increase alignment of symbols already placed in anchors Date: Tue, 10 Mar 2015 04:24:00 -0000 [thread overview] Message-ID: <bug-65355-4-3aaBsO25g5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65355-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65355 --- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Author: hubicka Date: Tue Mar 10 04:24:21 2015 New Revision: 221297 URL: https://gcc.gnu.org/viewcvs?rev=221297&root=gcc&view=rev Log: PR tree-optimization/65355 * varasm.c (notice_global_symbol): Do not produce RTL. * symtab.c (symtab_node::can_increase_alignment_p): Check for section anchor. * tree-vect-data-refs.c (vect_compute_data_ref_alignment): Do not check for section anchors. * gcc.dg/vect/section-anchors-vect-69.c: Update template. Modified: trunk/gcc/ChangeLog trunk/gcc/symtab.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/vect/section-anchors-vect-69.c trunk/gcc/tree-vect-data-refs.c trunk/gcc/varasm.c
next prev parent reply other threads:[~2015-03-10 4:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-08 23:34 [Bug tree-optimization/65355] New: [4.8/4.9 " hubicka at gcc dot gnu.org 2015-03-09 14:43 ` [Bug tree-optimization/65355] [4.8/4.9/5 " rguenth at gcc dot gnu.org 2015-03-10 4:24 ` hubicka at gcc dot gnu.org [this message] 2015-03-11 9:19 ` [Bug tree-optimization/65355] [4.8/4.9 " jakub at gcc dot gnu.org 2015-03-11 20:31 ` pthaugen at gcc dot gnu.org 2015-03-13 1:09 ` hubicka at gcc dot gnu.org 2015-06-23 8:19 ` rguenth at gcc dot gnu.org 2015-06-26 19:54 ` [Bug tree-optimization/65355] [4.9 " jakub at gcc dot gnu.org 2015-06-26 20:27 ` jakub 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-65355-4-3aaBsO25g5@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).