Snapshot gcc-6-20150913 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20150913/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
> It's not so much allowing signal handlers to be split stack. It's handling
> the case of a signal occurring while the stack is being split. That is not
> so very unlikely, and it will crash your program, as you get a SIGSEGV while
> trying to handle whatever signal just arrived.
I see. In w
> I can tell you a lot about the Go stack-copy implementation, I worked on a
> lot of it.
Thanks! Keith. I appreciate the insight.
> The big advantage is that you only have to copy once (amortized). The stack
> grows as big as you need it and then you don't need to do any more work from
> the
Sent from my iPhone
Jimmy Ginn
* Jeff Law:
> On 09/13/2015 12:28 PM, Florian Weimer wrote:
>> * Ajit Kumar Agarwal:
>>
>>> The replacement of malloc with alloca can be done on the following
>>> analysis.
>>>
>>> If the lifetime of an object does not stretch beyond the immediate
>>> scope. In such cases the malloc can be replace
On 09/13/2015 12:28 PM, Florian Weimer wrote:
* Ajit Kumar Agarwal:
The replacement of malloc with alloca can be done on the following
analysis.
If the lifetime of an object does not stretch beyond the immediate
scope. In such cases the malloc can be replaced with alloca. This
increases the p
On Sat, Sep 12, 2015 at 11:38 PM, Anders Oleson wrote:
>
> From examining the __morestack code, I found that the sigprocmask
> system call is being called (twice?!) per __morestack, even when it
> should just need to switch to the next allocated segment. I did read
> the reason for that change: to
* Ajit Kumar Agarwal:
> The replacement of malloc with alloca can be done on the following
> analysis.
>
> If the lifetime of an object does not stretch beyond the immediate
> scope. In such cases the malloc can be replaced with alloca. This
> increases the performance to a great extent.
You als
On 13/09/15 05:32, Ian Lance Taylor wrote:
On Sat, Sep 12, 2015 at 2:11 PM, David Kunsman wrote:
Hello...I am thinking about starting to hack on something and I found
https://gcc.gnu.org/wiki/Speedup_areas and one of the projects is a
multi-threaded linker. I am just wondering if this is stil
All:
The replacement of malloc with alloca can be done on the following analysis.
If the lifetime of an object does not stretch beyond the immediate scope. In
such cases the malloc can be replaced with alloca.
This increases the performance to a great extent.
Inlining helps to a great extent th
I can tell you a lot about the Go stack-copy implementation, I worked
on a lot of it. The big drawback is that you need to ensure that you
have accurate stack maps for all frames on the stack. This is
something we can do in Go with some work but would be more problematic
for C. Most of that work
11 matches
Mail list logo
