This is the mail archive of the
mailing list for the GCC project.
Re: [patches] Re: dwarf2/ACCUMULATE_OUTGOING_ARGS fix
>>>>> "Jan" == Jan Hubicka <firstname.lastname@example.org> writes:
>> > For use in debugger and in unwinding library for x86_64. For instance
>> > the garbage collector needs to unwind stack at any point.
>> It does? Why? How? What is this unwinding library of which you speak?
> When you have non-conservative garbage collector over multithreaded
> application. When such beast is activated it needs to parse stacks of
> all threads and thus needs to unwind stack at any state of execution.
Ah. I suppose the additional detail could be controlled with a flag (as it
already is somewhat, based on -fasynchronous-exceptions).
What unwinding library are you referring to?