From: Jeff Law <law@redhat.com>
To: Kito Cheng <kito@0xlab.org>,
gcc-patches@gcc.gnu.org, Jan Hubicka <hubicka@ucw.cz>,
Richard Sandiford <rsandifo@linux.vnet.ibm.com>,
Eric Botcazou <ebotcazou@adacore.com>
Subject: Re: [PATCH] Pass correct memory attributes for build constant
Date: Wed, 25 Jun 2014 21:01:00 -0000 [thread overview]
Message-ID: <53AB38AB.7040901@redhat.com> (raw)
In-Reply-To: <CA+yXCZCUgioKCimPVvvU10Zwc9a+TFBWBxjbU6pHLMkW8+YV3w@mail.gmail.com>
On 06/25/14 09:35, Kito Cheng wrote:
> Hi all:
> This patch is fix constant memory's symbol_ref don't have right
> alignment info since `exp` don't set alignment (and should not set
> alignment info for `exp`) , use `decl` to set_mem_attributes for
> right alignment info.
>
> ChangLog
> 2014-06-25 Kito Cheng <kito@0xlab.org>
>
> * varasm.c (build_constant_desc): Use decl to set mem
> attributes since exp don't have correct aligment info.
Do you have a testcase for this?
jeff
next prev parent reply other threads:[~2014-06-25 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 15:35 Kito Cheng
2014-06-25 21:01 ` Jeff Law [this message]
2014-06-26 3:38 ` Kito Cheng
2014-06-27 22:35 ` Jeff Law
2014-06-28 0:14 ` Jan Hubicka
2014-06-30 6:17 ` Kito Cheng
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=53AB38AB.7040901@redhat.com \
--to=law@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=kito@0xlab.org \
--cc=rsandifo@linux.vnet.ibm.com \
/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: link
Be 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).