This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Fix handling of very long asm statements in inliner
- From: Andi Kleen <andi at firstfloor dot org>
- To: Richard Earnshaw <rearnsha at arm dot com>
- Cc: Andi Kleen <andi at firstfloor dot org>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "hubicka at ucw dot cz" <hubicka at ucw dot cz>
- Date: Thu, 21 Feb 2013 16:59:06 +0100
- Subject: Re: [PATCH] Fix handling of very long asm statements in inliner
- References: <20130221140555.GE2928@two.firstfloor.org> <512635F3.firstname.lastname@example.org>
> That doesn't sound enough, unless there is already code out there
> that respects this count. 1000 at 4 bytes per instruction is only
> 4k. More that small enough for the rest of the compiler to think
> that it could jump around such blocks cheaply.
> I think a limit of 1M or more might be more appropriate.
I got an overflow for 6.4M, so 1M would be dangerously near that.
100k perhaps ?
This was not for jump shortening, but the inliner heuristics.
In the worst case we could separate the two, would be a larger