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: Mon, 04 May 2015 09:29:00 -0000 [thread overview]
Message-ID: <55473BF4.3010603@st.com> (raw)
In-Reply-To: <CAHFci28e4+dkooAQzLFjo2-TCAAV9HkMYuwRivNt8c4r4LD=Pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
> 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"
>
that is the same latent bug for aarch64: alignment flags are not
propagated with attribute optimize ("O2").
testing attached patch
Christian
[-- Attachment #2: align.patch --]
[-- Type: text/x-patch, Size: 1248 bytes --]
Index: config/aarch64/aarch64.c
===================================================================
--- config/aarch64/aarch64.c (revision 222627)
+++ config/aarch64/aarch64.c (working copy)
@@ -6908,18 +6908,6 @@
#endif
}
- /* If not opzimizing for size, set the default
- alignment to what the target wants */
- if (!optimize_size)
- {
- if (align_loops <= 0)
- align_loops = aarch64_tune_params->loop_align;
- if (align_jumps <= 0)
- align_jumps = aarch64_tune_params->jump_align;
- if (align_functions <= 0)
- align_functions = aarch64_tune_params->function_align;
- }
-
if (AARCH64_TUNE_FMA_STEERING)
aarch64_register_fma_steering ();
@@ -6935,6 +6923,18 @@
flag_omit_leaf_frame_pointer = false;
else if (flag_omit_leaf_frame_pointer)
flag_omit_frame_pointer = true;
+
+ /* If not opzimizing for size, set the default
+ alignment to what the target wants */
+ if (!optimize_size)
+ {
+ if (align_loops <= 0)
+ align_loops = aarch64_tune_params->loop_align;
+ if (align_jumps <= 0)
+ align_jumps = aarch64_tune_params->jump_align;
+ if (align_functions <= 0)
+ align_functions = aarch64_tune_params->function_align;
+ }
}
static struct machine_function *
next prev parent reply other threads:[~2015-05-04 9:29 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
2015-05-04 9:29 ` Christian Bruel [this message]
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=55473BF4.3010603@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).