Earl Chew wrote:
I can't make up my mind whether the new behaviour is incorrect,
or whether the old behaviour should never have been supported.
I'm pretty certain this is a defect because I can construct a
program that should work, but doesn't.
In any case, I've discovered that this was an abe
> Sometimes I have got a bus error at libstdc++ with gcc 3.4.2 in SUN.
I'm afraid the information you've given is pretty scant. Far more
information will be required, plus some work on your side to try and
isolate the problem.
Perhaps you could try reporting the problem to the g
Hi,
Sometimes I have got a bus error at libstdc++ with gcc
3.4.2
in SUN.
I have used a multithread 64 bits application that
loads dynamicly ( as a application's plugin ) a couple
of dinamic libraries. That application and all your
dynamic libraries have a strong use of C++ Standard
Lib
gcc version 3.4.2(linux sll) So I am migrating a
> component to this version from gcc 2.96.
>
> In my existing code I am using the *out_waiting* function of the struct
> streambuf present in the streambuf.h file.
>
> But I can't find this function in this version of gcc 3.
Hi,
I have moved to gcc version 3.4.2(linux sll) So I am migrating a
component to this version from gcc 2.96.
In my existing code I am using the *out_waiting* function of the struct
streambuf present in the streambuf.h file.
But I can't find this function in this version of gcc 3.4.2. so
oid bar(char*);
>
> void foo(int x)
> {
> if (x) { char y[4096]; bar(y); }
> else { char z[4096]; bar(z); }
> }
>
> Cygwin gcc 3.4.2 -O2 yields:
>
> pushl %ebp
> movl$8216, %eax /* Should be about 4k */
> movl
On Wednesday 04 May 2005 16:22, Earl Chew wrote:
> Can anyone tell me if there is a patch for this problem?
The patch is called GCC 4.0.
Gr.
Steven
Can anyone tell me if there is a patch for this problem?
Consider:
void bar(char*);
void foo(int x)
{
if (x) { char y[4096]; bar(y); }
else { char z[4096]; bar(z); }
}
Cygwin gcc 3.4.2 -O2 yields:
pushl %ebp
movl$8216, %eax /* Should be
Levent Erbuke wrote:
Is there a tool that retrieve which version of gcc was used to compile a
lib or anything else ?
It depends on the target, but use of strings in the .comment section is
fairly common. Try
objdump --section=.comment --full-contents
There will be one string for every object f
Hello all !
My app now crashes when compiled with gcc 3.4.2 (before I used gcc 3.3.5)
I read that this could be of ABI issues...
Is there a tool that retrieve which version of gcc was used to compile a
lib or anything else ?
It could be very helpfully to control i.e. libc, the qt lib, etc
Hello,
last comparison is here: http://gcc.gnu.org/ml/gcc/2005-01/msg01714.html
First of all, who has been this brave man/woman who fixed ir.cc
regressions? I would like to thank him/her! :-)
Well, the results are excelent and regressions (results worser than 5%)
are only those:
-O1: static.cc
but is thwarted because the value has been
lost.
I'm working with a port of dw2 based EH for powerpc VxWorks on
gcc 3.4.2. The compiler builds and is working. I have ported the EH
test from STLport, and most of the tests run.
(BTW the ported EH tests r
12 matches
Mail list logo
