On Jul 25, 2013, at 1:23 PM, Peter Bex wrote:
> The attached patch simply invokes the procedures with argument counts
> from zero to 50 and from MAX-50 to MAX (or rather from MAX to MAX-50,
> but that's nitpicking).
Looks good and tests even better. Pushed.
Jim
Nice. I'll check this out later today.
On Jul 25, 2013, at 13:23, Peter Bex wrote:
> On Thu, Jul 25, 2013 at 08:54:39AM +0200, Peter Bex wrote:
>> My initial thought was to only generate some calls near the edge cases,
>> instead of doing all the calls from 0 up to 2048 arguments.
>>
>> I'm uns
On Thu, Jul 25, 2013 at 08:54:39AM +0200, Peter Bex wrote:
> My initial thought was to only generate some calls near the edge cases,
> instead of doing all the calls from 0 up to 2048 arguments.
>
> I'm unsure how to best make it do this, and I was tired at the time so
> I kept it as-is. Maybe so
On Wed, Jul 24, 2013 at 02:27:47PM -0500, Jim Ursetto wrote:
> Although this patch looks good and tests out fine, during the tests, chicken
> bloats to 1GB and gcc to 500MB, and they take forever to build apply-test --
> probably because the .c file is 40MB! I'm not sure it's wise to apply as-is
Although this patch looks good and tests out fine, during the tests, chicken
bloats to 1GB and gcc to 500MB, and they take forever to build apply-test --
probably because the .c file is 40MB! I'm not sure it's wise to apply as-is;
it may kill some machines. Suggestions?
Jim
On Jul 24, 2013,
Hi all,
As we figured out in ticket #910, there are two problems when directly
invoking procedures with a large number of rest arguments (not via APPLY):
- there's a bug in GCC 4.5's code generation which causes random errors
like segfaults and illegal instructions to occur.
- even with a corr
