From: Andi Kleen <andi@firstfloor.org>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Andi Kleen <andi@firstfloor.org>,
Richard Earnshaw <rearnsha@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix handling of very long asm statements in inliner
Date: Thu, 21 Feb 2013 18:19:00 -0000 [thread overview]
Message-ID: <20130221181910.GI2928@two.firstfloor.org> (raw)
In-Reply-To: <20130221174627.GA13309@kam.mff.cuni.cz>
> So I am fine with the cutoff. We may need to add more overflow guards (we
> already have quite few for time) that makes me wonder if all this should not be
> done all in saturating arithmetic now when it can be done theoretically with one
> C++ class?
Sounds like a good idea, although I don't know how intrusive that is. But can
try.
Still would like to use the 1000 for the 4.7 backport. Ok?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2013-02-21 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 14:06 Andi Kleen
2013-02-21 14:58 ` Richard Earnshaw
2013-02-21 15:59 ` Andi Kleen
2013-02-21 17:02 ` Andi Kleen
2013-02-21 17:46 ` Jan Hubicka
2013-02-21 18:19 ` Andi Kleen [this message]
2013-02-22 3:32 ` Andi Kleen
2013-02-21 18:19 ` Richard Earnshaw
2013-09-08 19:50 ` *PING* " Andi Kleen
2013-09-08 23:23 ` Jan Hubicka
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=20130221181910.GI2928@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rearnsha@arm.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).