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] New: [4.8/4.9 Regression] vectorizer increase alignment of symbols already placed in anchors Date: Sun, 08 Mar 2015 23:34:00 -0000 [thread overview] Message-ID: <bug-65355-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65355 Bug ID: 65355 Summary: [4.8/4.9 Regression] vectorizer increase alignment of symbols already placed in anchors Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: hubicka at gcc dot gnu.org Increasing alignment of symbol does not work once RTL containing anchor was produced. Index: symtab.c =================================================================== --- symtab.c (revision 221268) +++ symtab.c (working copy) @@ -1924,6 +1924,13 @@ symtab_node::can_increase_alignment_p (v if (TREE_ASM_WRITTEN (target->decl)) return false; + /* If target is already placed in an anchor, we can not touch its + alignment. */ + if (DECL_RTL_SET_P (target->decl) + && MEM_P (DECL_RTL (target->decl)) + && SYMBOL_REF_HAS_BLOCK_INFO_P (XEXP (DECL_RTL (target->decl), 0))) + return false; + /* Constant pool entries may be shared. */ if (DECL_IN_CONSTANT_POOL (target->decl)) return false; sadly introduce quite few testsuite regressions for ppc-linux (checking that alignmnet was increased). This is because notice_global_symbol produces RTL early and thus blocks this. I suppose notice_global_symbol needs to be redone to work on tree only. For next stage1 we also probably want to drop the increase_alignmnets IPA pass and run all late tree passes prior RTL generation.
next reply other threads:[~2015-03-08 23:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-08 23:34 hubicka at gcc dot gnu.org [this message] 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 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@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).