From: Torsten Duwe <duwe@suse.de>
To: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: Li Bin <huawei.libin@huawei.com>, Jiri Kosina <jkosina@suse.cz>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] add -fprolog-pad=N option to c-family
Date: Thu, 28 Apr 2016 11:18:00 -0000 [thread overview]
Message-ID: <20160428111837.GB2637@suse.de> (raw)
In-Reply-To: <324F1C9E-0789-4290-B9B3-AC0C4027CB78@linaro.org>
On Thu, Apr 28, 2016 at 11:39:48AM +0300, Maxim Kuvyrkov wrote:
> > On Apr 27, 2016, at 6:22 PM, Torsten Duwe <duwe@suse.de> wrote:
>
> Your current patch is great for experiments for the kernel engineers to check if suggested approaches to code patching will work. Still, I prefer to implement LTO-friendly way of handling -fprolog-pad=N via function attributes.
That was exactly my intention. I only wanted *some* working compiler.
I'm sure you compiler people will have a better way to finally implement this.
All I can say so far about the ipa-ra issue is that it'd be great if
x9(?) could be left as volatile / scratch; the rest can be preserved.
Torsten
next prev parent reply other threads:[~2016-04-28 11:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 15:22 Torsten Duwe
2016-04-27 16:26 ` Szabolcs Nagy
2016-04-28 8:48 ` Maxim Kuvyrkov
2016-04-28 10:58 ` Szabolcs Nagy
2016-04-28 11:32 ` Torsten Duwe
2016-05-09 5:53 ` AKASHI Takahiro
2016-09-29 15:18 ` [PATCH v2] " Torsten Duwe
2016-09-30 9:59 ` Jose E. Marchesi
2016-09-30 10:22 ` Torsten Duwe
2016-10-03 9:45 ` AKASHI Takahiro
2016-10-04 21:46 ` Maxim Kuvyrkov
2016-12-06 14:02 ` Maxim Kuvyrkov
2016-04-28 8:40 ` [PATCH] " Maxim Kuvyrkov
2016-04-28 11:18 ` Torsten Duwe [this message]
2016-04-28 15:07 ` Jeff Law
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=20160428111837.GB2637@suse.de \
--to=duwe@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=huawei.libin@huawei.com \
--cc=jkosina@suse.cz \
--cc=maxim.kuvyrkov@linaro.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: 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).