Re: porting to amd64-freebsd

If it helps, I'm pretty sure that some changes that I made in the 2012.1
release should help to reduce the stack usage some. The problems that
existed before on x86-64 linux aren't as bad now as they used to be.

 - Bruce



On Mon, Jan 14, 2013 at 10:17 AM, <[email protected]> wrote:

> Hello,
>
>
> On Mon, 14 Jan 2013 11:05:02 +0900, Bruce Mitchener <
> [email protected]> wrote:
>
>> Usually you can do this via ulimit at the shell level:
>>
>>     ulimit -s 16384
>>
> In FreeBSD, the stack size of primary thread is hard coded. I can't
> increase it by any way.
> the only way to increase it is to recompile the thread library. I don't
> want to do it.
> I had trying to fake mmaped space as the stack. It seems to have succeeded.
> I've got Stage2 dylan-compiler. and building the Stage3 is succeeded.
> --
> HIROSHI OOTA
>
>
>>  - Bruce
>>
>>
>> On Mon, Jan 14, 2013 at 6:19 AM, <[email protected].**jp<[email protected]>>
>> wrote:
>>
>>  Hello,
>>>
>>>
>>> On Sat, 12 Jan 2013 22:49:17 +0900, Hannes Mehnert <[email protected]>
>>> wrote:
>>>
>>>  For that I needed to increase the stack size - maybe you need to do
>>>> that?
>>>>
>>>>  when I encounter to SEGV, the $rsp points stack guard address.
>>> perhaps cause of SEGV is the stack shortage.
>>>
>>> I found this article.
>>> http://lists.freebsd.org/****pipermail/freebsd-hackers/**<http://lists.freebsd.org/**pipermail/freebsd-hackers/**>
>>> 2008-January/022916.html<http:**//lists.freebsd.org/pipermail/**
>>> freebsd-hackers/2008-January/**022916.html<http://lists.freebsd.org/pipermail/freebsd-hackers/2008-January/022916.html>
>>> >
>>>
>>> it says
>>> | There is no way in FreeBSD to do the same for initial stack size for
>>> the
>>> | main thread.  No runtime, no linktime, no nada nichego.  Apparently,
>>> the
>>> | only way to increase it is to recompile your threaded library, which
>>> will
>>> | have a system-wide effect.
>>>
>>> It seems  I need some trick to solve it.
>>> --
>>> HIROSHI OOTA
>>>
>>>
>>>
>>>  I think also it started to fail after some changes to the C runtime in
>>>> 2012.
>>>> You might first want to check whether the C runtime works fine on
>>>> FreeBSD and 32 bit (single and multi-threaded).
>>>>
>>>>
>>>> Hannes
>>>> ______________________________****_________________
>>>> hackers mailing list
>>>> [email protected]
>>>> https://lists.opendylan.org/****mailman/listinfo/hackers<https://lists.opendylan.org/**mailman/listinfo/hackers>
>>>> <https**://lists.opendylan.org/**mailman/listinfo/hackers<https://lists.opendylan.org/mailman/listinfo/hackers>
>>>> >
>>>>
>>>>  ______________________________****_________________
>>> hackers mailing list
>>> [email protected]
>>> https://lists.opendylan.org/****mailman/listinfo/hackers<https://lists.opendylan.org/**mailman/listinfo/hackers>
>>> <https**://lists.opendylan.org/**mailman/listinfo/hackers<https://lists.opendylan.org/mailman/listinfo/hackers>
>>> >
>>>
>> ______________________________**_________________
> hackers mailing list
> [email protected]
> https://lists.opendylan.org/**mailman/listinfo/hackers<https://lists.opendylan.org/mailman/listinfo/hackers>
>

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers