It looks like modifying the testsuite scripts for libgomp
to properly compile c++ files with g++ will be pretty messy.
Can we just fix PR30703 for now with the simple change...
Index: libgomp/testsuite/libgomp.c++/pr30703.C
===
/u
On Mar 14, 2007, at 2:11 AM, Jakub Jelinek wrote:
On Tue, Mar 13, 2007 at 10:28:41PM -0400, Jack Howarth wrote:
Interestingly, while...
gcc-4 pr30703.C -fmessage-length=0 -fopenmp -O0 -L/sw/lib/gcc4.2/
lib -lgomp -lstdc++ -lm -m32 -o ./pr30703.exe
Could we please use g++ to compile C++ c
Jakub,
So shouldn't we either XFAIL pr30703.C on *-apple-darwin* or
specify that the -shared-libgcc flag should be used on that
target for pr30703.C?
Jack
On Wed, Mar 14, 2007 at 10:11:35AM +0100, Jakub Jelinek wrote:
> On Tue, Mar 13, 2007 at 10:28:41PM -0400, Jack Howarth wrot
On Tue, Mar 13, 2007 at 10:28:41PM -0400, Jack Howarth wrote:
> Interestingly, while...
>
> gcc-4 pr30703.C -fmessage-length=0 -fopenmp -O0 -L/sw/lib/gcc4.2/lib -lgomp
> -lstdc++ -lm -m32 -o ./pr30703.exe
> /usr/bin/ld: Undefined symbols:
> __Unwind_Resume
> collect2: ld returned 1 exit statu
Interestingly, while...
gcc-4 pr30703.C -fmessage-length=0 -fopenmp -O0 -L/sw/lib/gcc4.2/lib -lgomp
-lstdc++ -lm -m32 -o ./pr30703.exe
/usr/bin/ld: Undefined symbols:
__Unwind_Resume
collect2: ld returned 1 exit status
fails on powerpc-apple-darwin8
gcc-4 pr30703.C -fmessage-length=0 -f
I am noticing one other issue with current gcc 4.2 branch
on powerpc-apple-darwin8. We seem to have failures for the
following libgomp testsuite tests...
FAIL: libgomp.c++/pr30703.C -O0 (test for excess errors)
WARNING: libgomp.c++/pr30703.C -O0 compilation failed to produce executable
FAI
