"Terry Guo" writes:
> Ah, you are right. I just thought the "make -k" should keep going
It does.
> and omit all the errors.
It reports _all_ (independent) errors, not just the first one.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 4
>
> "Terry Guo" writes:
>
> > make[1]: *** [check-recursive] Error 1
> > make[1]: Target `check' not remade because of errors.
> > make[1]: Leaving directory
> > `/home/build/gcc-4-7-daily-test/build-linux/gcc-final/arm-none-
> eabi/libstdc+
> > +-v3'
> > make: *** [check-target-libstdc++-v3] E
"Terry Guo" writes:
> make[1]: *** [check-recursive] Error 1
> make[1]: Target `check' not remade because of errors.
> make[1]: Leaving directory
> `/home/build/gcc-4-7-daily-test/build-linux/gcc-final/arm-none-eabi/libstdc+
> +-v3'
> make: *** [check-target-libstdc++-v3] Error 2
> make: Target `
On 17 February 2011 17:26, Pascal Francq wrote:
> In fact, since it is related on how g++ is implementing its heritage mechanism
> in C++, I was thinking it was the right mailing-list. In fact, by adding a
> convenient method in Super2, the code compiles :
> template inline void Test(C* ptr)
In fact, since it is related on how g++ is implementing its heritage mechanism
in C++, I was thinking it was the right mailing-list. In fact, by adding a
convenient method in Super2, the code compiles :
template inline void Test(C* ptr) {Super::Test(ptr);}
This trick let me suppose that a
On 17 February 2011 11:03, Pascal Francq wrote:
>
> Is this a problem related to a misunderstood concept from me, a wrong
> implementation or a technical problem of g++ ?
In any of those cases, such questions are off-topic on this mailing
list, which is for development of gcc, not help using it.
Hi,
While compiling the following code, I got an error :
template class Super
{
public:
Super(void) {}
void Test(C*) {}
};
class A
{
public:
A(void) {}
};
class A1 : public A
{
public:
A1(void) : A() {}
};
class A2 : public A
{
public:
A2(void) : A() {}
"Eric Lemings" <[EMAIL PROTECTED]> writes:
> If anyone can shed some light on the strange behavior in the C++
> program,
This is not the appropriate forum, which is about development of GCC, for
such questions. Please use [EMAIL PROTECTED] or a general programming
f
Greetings,
While writing a generic C++ algoririthm for base64 encoding, I came
across
some very strange behavior. If you take the following program
(admittedly
verbose for debugging purposes) and test it on some data, say the logo
image
from www.google.com, you may notice (depending on your
"Mohamed Shafi" <[EMAIL PROTECTED]> writes:
> /* { dg-final { scan-tree-dump "b4 = 6.3e+1" "gimple" } } */
Note that scan-tree-dump takes a regular expression. So you are
looking for '6' followed by any character followed by '3' followed by
one or more 'e's followed by '1'.
Ian
Hello all,
I added few testcases to the existing testsuite in gcc 4.1.1 for a
private target.
After running the testsuite i found out that all my test cases with
scan-tree-dump testing failed for one particular situation.
The values are scanned from gimple tree dump and its fails for cases like
11 matches
Mail list logo
