public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61296] Excessive alignment in ix86_data_alignment Date: Wed, 17 Dec 2014 14:23:00 -0000 [thread overview] Message-ID: <bug-61296-4-Ru2uBb6d3g@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61296-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61296 --- Comment #16 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> --- Author: hjl Date: Wed Dec 17 14:22:57 2014 New Revision: 218818 URL: https://gcc.gnu.org/viewcvs?rev=218818&root=gcc&view=rev Log: Add -malign-data={abi|compat|cachineline} Add -malign-data={abi|compat,cachineline} to control how GCC aligns variables. "compat" uses increased alignment value compatible with GCC 4.8 and earlier, "abi" uses alignment value as specified by the psABI, and "cacheline" uses increased alignment value to match the cache line size. "compat" is the default. gcc/ PR target/61296 * config/i386/i386-opts.h (ix86_align_data): New enum. * config/i386/i386.c (ix86_data_alignment): Return the ABI alignment value for -malign-data=abi, the cachine line size for -malign-data=cachineline and the older GCC compatible alignment value for for -malign-data=compat. * config/i386/i386.opt (malign-data=): New. * doc/invoke.texi: Document -malign-data=. gcc/testsuite/ PR target/61296 * gcc.target/i386/pr61296-2.c: New. * gcc.target/i386/pr61296-2.c: Likewise. * gcc.target/i386/pr61296-3.c: Likewise. * gcc.target/i386/pr61296-4.c: Likewise. * gcc.target/i386/pr61296-5.c: Likewise. * gcc.target/i386/pr61296-6.c: Likewise. * gcc.target/i386/pr61296-7.c: Likewise. Added: trunk/gcc/testsuite/gcc.target/i386/pr61296-1.c trunk/gcc/testsuite/gcc.target/i386/pr61296-2.c trunk/gcc/testsuite/gcc.target/i386/pr61296-3.c trunk/gcc/testsuite/gcc.target/i386/pr61296-4.c trunk/gcc/testsuite/gcc.target/i386/pr61296-5.c trunk/gcc/testsuite/gcc.target/i386/pr61296-6.c trunk/gcc/testsuite/gcc.target/i386/pr61296-7.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386-opts.h trunk/gcc/config/i386/i386.c trunk/gcc/config/i386/i386.opt trunk/gcc/doc/invoke.texi trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-12-17 14:23 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-23 16:49 [Bug target/61296] New: " hjl.tools at gmail dot com 2014-05-27 18:23 ` [Bug target/61296] " hjl.tools at gmail dot com 2014-05-30 16:52 ` hjl.tools at gmail dot com 2014-06-11 16:38 ` hjl.tools at gmail dot com 2014-12-11 17:21 ` hubicka at gcc dot gnu.org 2014-12-11 17:33 ` jakub at gcc dot gnu.org 2014-12-11 17:38 ` hjl.tools at gmail dot com 2014-12-11 23:25 ` jakub at gcc dot gnu.org 2014-12-16 13:21 ` hjl.tools at gmail dot com 2014-12-16 13:31 ` jakub at gcc dot gnu.org 2014-12-16 13:41 ` hjl.tools at gmail dot com 2014-12-16 13:47 ` jakub at gcc dot gnu.org 2014-12-16 13:53 ` hjl.tools at gmail dot com 2014-12-16 13:58 ` jakub at gcc dot gnu.org 2014-12-16 15:51 ` hjl.tools at gmail dot com 2014-12-16 19:24 ` hjl.tools at gmail dot com 2014-12-17 14:23 ` hjl at gcc dot gnu.org [this message] 2014-12-17 14:50 ` hjl.tools at gmail dot com 2021-09-12 7:47 ` pinskia 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-61296-4-Ru2uBb6d3g@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).