Displaying 3 results from an estimated 3 matches for "gtp_input".
2019 Feb 07
2
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
...000000000041926d in genmove_conservative (i=i at entry=0x7fffffffd36c, j=j at entry=0x7fffffffd368, color=3) at engine/genmove.c:255
#7 0x00000000004618ae in gtp_gg_genmove (s=<optimized out>) at interface/play_gtp.c:2163
#8 0x000000000045b0f8 in gtp_main_loop (commands=<optimized out>, gtp_input=0xb8b100) at interface/gtp.c:126
Figure 1: Backtrace with @entry value parameters
Cost in disk image size increase and compile-time
The parameter-entry-value feature is enabled with -g compilation. Due to new DebugInfo metadata generation which adds entries to DWARF sections such as .debug_info an...
2019 Feb 08
3
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
...n genmove_conservative (i=i at entry=0x7fffffffd36c, j=j at entry=0x7fffffffd368, color=3) at engine/genmove.c:255
> #7 0x00000000004618ae in gtp_gg_genmove (s=<optimized out>) at interface/play_gtp.c:2163
> #8 0x000000000045b0f8 in gtp_main_loop (commands=<optimized out>, gtp_input=0xb8b100) at interface/gtp.c:126
> Figure 1: Backtrace with @entry value parameters
Very nice!
>
> Cost in disk image size increase and compile-time
> The parameter-entry-value feature is enabled with -g compilation. Due to new DebugInfo metadata generatio...
2019 Feb 08
2
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
...ffd36c, j=j at entry=0x7fffffffd368, color=3) at
> engine/genmove.c:255
> > #7 0x00000000004618ae in gtp_gg_genmove (s=<optimized out>) at
> interface/play_gtp.c:2163
> > #8 0x000000000045b0f8 in gtp_main_loop (commands=<optimized out>,
> gtp_input=0xb8b100) at interface/gtp.c:126
> > Figure 1: Backtrace with @entry value parameters
>
> Very nice!
>
> >
> > Cost in disk image size increase and compile-time
> > The parameter-entry-value feature is enabled with -...