Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Gabriel Dos Reis
On Tue, Nov 20, 2012 at 6:16 PM, Lawrence Crowl wrote: > And, as a side note, highly formatted output generally is not > much better than printf. For any text that needs to be localized, > I recommend that we stick with what we have. I agree with Lawrence that for texts that need localization,

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Gabriel Dos Reis
On Tue, Nov 20, 2012 at 7:01 PM, Xinliang David Li wrote: > Right -- gdb does not know the complete type of std::cout and > std::cerr -- try the following program with -g and invoke print, or << > in the debugger -- see what you will get: Is this because the hack we (libstdc++ folks) used to defi

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Theodore Papadopoulo
On 11/21/2012 02:01 AM, Xinliang David Li wrote: Right -- gdb does not know the complete type of std::cout and std::cerr -- try the following program with -g and invoke print, or << in the debugger -- see what you will get: But that also suggest that the debugging experience needs for some imp

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Gabriel Dos Reis
On Wed, Nov 21, 2012 at 5:37 AM, Theodore Papadopoulo wrote: > On 11/21/2012 02:01 AM, Xinliang David Li wrote: >> >> Right -- gdb does not know the complete type of std::cout and >> std::cerr -- try the following program with -g and invoke print, or << >> in the debugger -- see what you will get:

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Michael Matz
Hi, On Tue, 20 Nov 2012, Lawrence Crowl wrote: > On 11/19/12, Diego Novillo wrote: > > On Nov 19, 2012 Michael Matz wrote: > > > So, yes, the larger layouting should be determined by name of the > > > dump function. A flag argument might look nice from an interface > > > design perspective, bu

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Tobias Grosser
On 11/20/2012 08:32 PM, Basile Starynkevitch wrote: On Tue, Nov 20, 2012 at 11:24:40AM -0800, Lawrence Crowl wrote: [] All of these functions come in two forms. function (FILE *, item_to_dump, formatting) function (item_to_dump, formatting) Since we have switched to C++, it wo

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Gabriel Dos Reis
On Wed, Nov 21, 2012 at 7:07 AM, Tobias Grosser wrote: > On 11/20/2012 08:32 PM, Basile Starynkevitch wrote: >> >> On Tue, Nov 20, 2012 at 11:24:40AM -0800, Lawrence Crowl wrote: >> [] > > All of these functions come in two forms. > > function (FILE *, item_to_dump, forma

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Tobias Grosser
On 11/21/2012 02:33 PM, Gabriel Dos Reis wrote: On Wed, Nov 21, 2012 at 7:07 AM, Tobias Grosser wrote: On 11/20/2012 08:32 PM, Basile Starynkevitch wrote: On Tue, Nov 20, 2012 at 11:24:40AM -0800, Lawrence Crowl wrote: [] All of these functions come in two forms. function (FILE

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Gabriel Dos Reis
On Wed, Nov 21, 2012 at 7:48 AM, Tobias Grosser wrote: > Is it correct to state that every translation unit that includes iostream > will include the iostream static constructors? C++ requires the definitions of globals such as std::cin, std::cout, and std::cerr that must be contructed (by any m

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Tobias Grosser
On 11/21/2012 03:25 PM, Gabriel Dos Reis wrote: On Wed, Nov 21, 2012 at 7:48 AM, Tobias Grosser wrote: Is it correct to state that every translation unit that includes iostream will include the iostream static constructors? C++ requires the definitions of globals such as std::cin, std::cout,

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Gabriel Dos Reis
I forgot to add this important information: you don't get the nifty counters if you don't include . Specifically. That means including or does not introduce any nifty counter. Including , which allows you to perform in-memory formatted IO, does not introduce any nifty counter. Said, differently

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Ian Lance Taylor
On Wed, Nov 21, 2012 at 3:18 AM, Gabriel Dos Reis wrote: > On Tue, Nov 20, 2012 at 6:16 PM, Lawrence Crowl wrote: > >> And, as a side note, highly formatted output generally is not >> much better than printf. For any text that needs to be localized, >> I recommend that we stick with what we have

Re: Unifying the GCC Debugging Interface

2012-11-21 Thread Gabriel Dos Reis
On Wed, Nov 21, 2012 at 9:02 AM, Ian Lance Taylor wrote: > On Wed, Nov 21, 2012 at 3:18 AM, Gabriel Dos Reis > wrote: >> On Tue, Nov 20, 2012 at 6:16 PM, Lawrence Crowl wrote: >> >>> And, as a side note, highly formatted output generally is not >>> much better than printf. For any text that nee

Re: -fPIC -fPIE

2012-11-21 Thread Paolo Bonzini
Il 14/11/2012 15:27, Ian Lance Taylor ha scritto: > On Wed, Nov 14, 2012 at 5:36 AM, Richard Earnshaw wrote: >> On 13/11/12 14:56, Ian Lance Taylor wrote: >>> >>> Currently -fPIC -fPIE seems to be the same as -fPIE. Unfortunately, >>> -fPIE -fPIC also seems to be the same as -fPIE. It seems to m

removing forced labels triggers assertion in dwarf info generation

2012-11-21 Thread Paulo Matos
Hello, I am facing some trouble with the following code (reduced with c-reduce): fn1 (ip) int *ip; { int x = 0; int *a; base: x++; if (x == 4) return; *a++ = 1; goto *&&base + *ip++; } The problems lies in the label base. Label base is added to the forced_labels li

Re: -fPIC -fPIE

2012-11-21 Thread Ian Lance Taylor
On Wed, Nov 21, 2012 at 8:56 AM, Paolo Bonzini wrote: > Il 14/11/2012 15:27, Ian Lance Taylor ha scritto: >> On Wed, Nov 14, 2012 at 5:36 AM, Richard Earnshaw wrote: >>> On 13/11/12 14:56, Ian Lance Taylor wrote: Currently -fPIC -fPIE seems to be the same as -fPIE. Unfortunately,

RFC - Initial planning for next Cauldron workshop

2012-11-21 Thread Diego Novillo
Ian and I have started thinking about the next Cauldron. This time, we are thinking of organizing it in Mountain View, at Google's headquarters. Dates are not yet set in stone, but these are some likely details: - The workshop would last 3 days, just like the Prague meeting. - Dates: We are look

Re: DWARF location descriptor and multi-register frame pointer

2012-11-21 Thread Michael Eager
On 11/20/2012 02:22 AM, Senthil Kumar Selvaraj wrote: How are frame pointer registers that span more than one hard register handled? Would it be appropriate to check the mode and do a multiple_reg_loc_descriptor call or something similar to handle this case? There is no requirement that

[cxx-conversion] Merge from trunk rev 193681

2012-11-21 Thread Diego Novillo
Now that we are out of stage 1, the next wave of cleanups will go into the cxx-conversion branch. I figured it was easier to revive this branch than open a new one. I just merged trunk at rev 193681 and updated the failures manifest in the branch (contrib/testsuite-management/*.xfail) so it's eas

Re: RFC - Initial planning for next Cauldron workshop

2012-11-21 Thread Ian Lance Taylor
On Wed, Nov 21, 2012 at 11:27 AM, Diego Novillo wrote: > Ian and I have started thinking about the next Cauldron. This > time, we are thinking of organizing it in Mountain View, at > Google's headquarters. In case it's not obvious, this is Mountain View, California, USA. > - Dates: We are looki

Re: -fPIC -fPIE

2012-11-21 Thread Paolo Bonzini
On Wed, Nov 21, 2012 at 8:02 PM, Ian Lance Taylor wrote: >> The main advantage is that you can compile a program with CFLAGS="-O2 -g >> -fPIE", and libtool's adding of -fPIC for shared libraries will work >> reliably. If -fPIE can still override -fPIC, the result depends on >> whether -fPIC comes

Re: -fPIC -fPIE

2012-11-21 Thread Ian Lance Taylor
On Wed, Nov 21, 2012 at 1:20 PM, Paolo Bonzini wrote: > On Wed, Nov 21, 2012 at 8:02 PM, Ian Lance Taylor wrote: >>> The main advantage is that you can compile a program with CFLAGS="-O2 -g >>> -fPIE", and libtool's adding of -fPIC for shared libraries will work >>> reliably. If -fPIE can still