public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christian Bruel <christian.bruel@st.com>
To: "Bin.Cheng" <amker.cheng@gmail.com>, Uros Bizjak <ubizjak@gmail.com>
Cc: Richard Henderson <rth@redhat.com>, Jan Hubicka <hubicka@ucw.cz>,
	       "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, x86] Add TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE hook
Date: Thu, 30 Apr 2015 08:43:00 -0000	[thread overview]
Message-ID: <5541E9E8.1020305@st.com> (raw)
In-Reply-To: <CAHFci28e4+dkooAQzLFjo2-TCAAV9HkMYuwRivNt8c4r4LD=Pg@mail.gmail.com>

OK I've have a look,

thanks

Christian


On 04/30/2015 10:27 AM, Bin.Cheng wrote:
> On Mon, Apr 27, 2015 at 8:01 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
>> On Wed, Feb 4, 2015 at 2:21 PM, Christian Bruel <christian.bruel@st.com> wrote:
>>> While trying to reduce the PR64835 case for ARM and x86, I noticed that the
>>> alignment flags are cleared for x86 when attribute optimized is used.
>>>
>>> With the attached testcases, the visible effects are twofold :
>>>
>>> 1) Functions compiled in with attribute optimize (-O2) are not aligned as if
>>> they were with the -O2 flag.
>>>
>>> 2) can_inline_edge_p fails because opts_for_fn (caller->decl) != opts_for_fn
>>> (callee->decl)) even-though they are compiled with the same optimization
>>> level.
>>
>> 2015-02-06  Christian Bruel  <christian.bruel@st.com>
>>
>>     PR target/64835
>>     * config/i386/i386.c (ix86_default_align): New function.
>>     (ix86_override_options_after_change): Call ix86_default_align.
>>     (TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE): New hook.
>>     (ix86_override_options_after_change): New function.
>>
>> 2015-02-06  Christian Bruel  <christian.bruel@st.com>
>>
>>     PR target/64835
>>     * gcc.dg/ipa/iinline-attr.c: New test.
>>     * gcc.target/i386/iinline-attr-2.c: New test.
>>
>> OK for mainline.
> 
> Hi Christian,
> I noticed case gcc.dg/ipa/iinline-attr.c failed on aarch64.  The
> original patch is x86 specific, while the case is added as general
> one.  Could you please have a look at this?
> 
> FAIL: gcc.dg/ipa/iinline-attr.c scan-ipa-dump inline
> "hooray[^\\n]*inline copy in test"
> 
> Thanks,
> bin
>>
>> Thanks,
>> Uros

  reply	other threads:[~2015-04-30  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 13:21 Christian Bruel
2015-04-27 12:01 ` Uros Bizjak
2015-04-30  8:38   ` Bin.Cheng
2015-04-30  8:43     ` Christian Bruel [this message]
2015-05-04  9:29     ` Christian Bruel
2015-05-05  9:11       ` Yvan Roux
2015-05-05  9:45         ` Christian Bruel

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=5541E9E8.1020305@st.com \
    --to=christian.bruel@st.com \
    --cc=amker.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=rth@redhat.com \
    --cc=ubizjak@gmail.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).