From: Jeff Law <law@redhat.com>
To: "rohitarulraj@freescale.com" <rohitarulraj@freescale.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"rguenther@suse.de" <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>
Cc: Alan Modra <amodra@gmail.com>, David Edelsohn <dje.gcc@gmail.com>,
Edmar Wienskoski <edmar@freescale.com>
Subject: Re: [RFC: Patch, PR 60158] gcc/varasm.c : Pass actual alignment value to output_constant_pool_2
Date: Tue, 28 Apr 2015 18:37:00 -0000 [thread overview]
Message-ID: <553FCEC6.8030609@redhat.com> (raw)
In-Reply-To: <BLUPR03MB1458002E9FF7B37BD72093E5C2E80@BLUPR03MB1458.namprd03.prod.outlook.com>
On 04/28/2015 03:44 AM, rohitarulraj@freescale.com wrote:
> Ping.
>
> -----Original Message-----
> From: Dharmakan Rohit-B30502
> Sent: Friday, March 27, 2015 7:57 PM
> To: gcc-patches@gcc.gnu.org; rguenther@suse.de; Jakub Jelinek
> Cc: Alan Modra; David Edelsohn; Wienskoski Edmar-RA8797; Dharmakan Rohit-B30502
> Subject: RE: [RFC: Patch, PR 60158] gcc/varasm.c : Pass actual alignment value to output_constant_pool_2
>
> Hi,
>
> I would like to resubmit these patches for comments. The previous detailed discussion is available in the below mentioned link.
> https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01679.html
> https://gcc.gnu.org/ml/gcc-patches/2014-05/msg00489.html
>
> The issue is still reproducible on GCC v4.8 branch.
>
> I have tested both the attached patches with e500v2 tool chain on GCC v4.8 branch [rev 221667] and GCC trunk [rev 221310] with no regressions.
>
> Patch1 [gcc.fix_pr60158_fixup_table_fsf_1]: Pass actual alignment value to output_constant_pool_2.
> Patch2 [gcc.fix_pr60158_fixup_table_fsf_2]: Use the alignment data available in the first argument (constant_descriptor_rtx) of output_constant_pool_1.
> (Note: this generates ".align" directive twice).
Are you asking for both patches to be applied or just one?
Jeff
next prev parent reply other threads:[~2015-04-28 18:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 14:27 rohitarulraj
2015-04-28 10:06 ` rohitarulraj
2015-04-28 18:37 ` Jeff Law [this message]
2015-04-28 18:46 ` rohitarulraj
2015-04-28 22:46 ` Jeff Law
2015-04-29 10:43 ` rohitarulraj
2015-04-30 15:15 ` Jeff Law
2015-04-30 15:44 ` rohitarulraj
2015-04-30 15:55 ` Jeff Law
2015-05-05 7:59 ` rohitarulraj
2015-05-15 5:01 ` Jeff Law
2015-05-15 10:38 ` Dharmakan Rohit Arul Raj
2015-05-15 17:53 ` Jeff Law
2015-05-18 8:00 ` Richard Biener
2015-05-25 8:21 ` Dharmakan Rohit Arul Raj
2015-05-26 8:49 ` Richard Biener
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=553FCEC6.8030609@redhat.com \
--to=law@redhat.com \
--cc=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=edmar@freescale.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
--cc=rohitarulraj@freescale.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).