You are right, it's my fault.
thanks a lot
Carrot
On Fri, Mar 29, 2013 at 6:33 PM, Alan Modra wrote:
> On Fri, Mar 29, 2013 at 04:58:50PM -0700, Carrot Wei wrote:
>> /trunkbin/bin/gcc -c -o rtl.o -DSPEC_CPU -DNDEBUG -I. -O2
>> -DSPEC_CPU_LP64 -m32rtl.c
>
> You've given contradictory opti
Hey guys,
I'm still planning to rewrite the c++ parser in GCC, right now I am still
researching, I remember a page that talked about the problems of parsing > in
nested templates, and I cannot find the link!
Searching for it has yielded people asking questions about errors where >>
occurs.
Pl
On Mon, Apr 1, 2013 at 8:55 AM, Alec Teal wrote:
>
> I'm still planning to rewrite the c++ parser in GCC, right now I am still
> researching, I remember a page that talked about the problems of parsing > in
> nested templates, and I cannot find the link!
>
> Searching for it has yielded people a
Hi,
replacing my AMD Phenom2 with a AMD Piledriver (Bulldozer Version2)
was reason enough for me to recompile gcc (and the whole linux-system)
with hard optimisation set to bdver2 (as I've done since my first
linux on an 68030).
But this time an increasing number of errors makes me a little bit ne
On 01/04/13 17:41, Ian Lance Taylor wrote:
On Mon, Apr 1, 2013 at 8:55 AM, Alec Teal wrote:
I'm still planning to rewrite the c++ parser in GCC, right now I am still
researching, I remember a page that talked about the problems of parsing > in
nested templates, and I cannot find the link!
S
On 1 April 2013 20:43, Alec Teal wrote:
>> I don't have a link, but it seems to me that the issue is obvious.
>> The C++ lexer recognizes >> as a single token. So when you write
>> std::vector>
>> the final >> is parsed as a single token, rather than the two separate
>> tokens that the parser
On 01/04/13 21:08, Jonathan Wakely wrote:
On 1 April 2013 20:43, Alec Teal wrote:
[snip]
Yes that is (was) the problem, I remember reading a document online, I cannot
recall where that looked at three ways of solving it and evaluated them, I know
of the problem but I want that guy's evaluati
On 03/30/2013 02:23 AM, Senthil Kumar Selvaraj wrote:
I couldn't find a way to ask gcc to just generate DWARF (default
version) either. How should this be fixed?
Maybe we could use -gdwarf for that now, since we stopped using it for
DWARF 1 in GCC 3.4.
Jason
On Apr 1, 2013, at 6:43 PM, Jason Merrill wrote:
> On 03/30/2013 02:23 AM, Senthil Kumar Selvaraj wrote:
>> I couldn't find a way to ask gcc to just generate DWARF (default
>> version) either. How should this be fixed?
>
> Maybe we could use -gdwarf for that now, since we stopped using it for DWA
