Hello All,
I am working on supporting call-stack debugging information for AVR
port. DWARF2 is already supported in gcc-4.4.3 but not call-stack
debug info. GCC internals document refers to INCOMING_RETURN_ADDR_RTX
and RTX_FRAME_RELATED_P. Incase of AVR, there is no link register.
Return addres
Snapshot gcc-4.4-20101228 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20101228/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.4 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
> I'm planning to add a set of new performance diagnostics to the
> libstdc++ profile mode
> (http://gcc.gnu.org/onlinedocs/libstdc++/manual/profile_mode.html) and
> am trying to come up with a list of what diagnostics are most
> meaningful and most wanted.
>
> At this (brainstorming) point I'm lo
Your first example points to a weakness in the compiler optimization.
If base_string constructor is inlined, the compiler should be able to
figure out both 'name' and the heap memory it points to can not be
modified by the call to notify, and therefore hoist access name.c_str
() and name.length ()
