public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/31640] cache block alignment is too aggressive on sh-elf Date: Fri, 02 Mar 2012 20:57:00 -0000 [thread overview] Message-ID: <bug-31640-4-TvdY4Z4wo4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-31640-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31640 --- Comment #5 from Oleg Endo <olegendo at gcc dot gnu.org> 2012-03-02 20:56:50 UTC --- Author: olegendo Date: Fri Mar 2 20:56:46 2012 New Revision: 184825 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184825 Log: PR target/31640 * config/sh/sh.h (LOOP_ALIGN): Move logic to sh_loop_align. * config/sh/sh.c: Update copyright notice dates. (sh_loop_align): Add logic from LOOP_ALIGN. Don't disable loop alignment for TARGET_HARD_SH4. (sh_option_override): Reduce default function alignment. Set loop alignment to 4 bytes when not optimizing for size. Modified: trunk/gcc/ChangeLog trunk/gcc/config/sh/sh.c trunk/gcc/config/sh/sh.h
next prev parent reply other threads:[~2012-03-02 20:57 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-31640-4@http.gcc.gnu.org/bugzilla/> 2011-12-31 17:29 ` oleg.endo@t-online.de 2012-02-26 23:33 ` olegendo at gcc dot gnu.org 2012-03-02 20:57 ` olegendo at gcc dot gnu.org [this message] 2012-03-19 19:36 ` olegendo at gcc dot gnu.org 2007-04-20 8:33 [Bug target/31640] New: cache align " chrbr at gcc dot gnu dot org 2007-04-20 8:57 ` [Bug target/31640] cache block " chrbr at gcc dot gnu dot org 2007-04-20 13:13 ` chrbr at gcc dot gnu dot org 2007-04-20 14:51 ` chrbr 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=bug-31640-4-TvdY4Z4wo4@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).