fix for 48208 and 48260 on darwin

[Christian Schüler]

Ok so I needed to install dejagnu from macports.
The comparison of the test results turned out empty except one output 
that made no sense:
----------

Tests that now fail, but worked before:

g++.dg/warn/Wstrict-aliasing-float-ref-int-obj.C  (test for warnings, 
line 7)

Tests that now work, but didn't before:

g++.dg/warn/Wstrict-aliasing-float-ref-int-obj.C  (test for warnings, 
line 7)

-----------
There was also this:

sed: 1: "/#if[ \t]*!defined(__cpl ...": command c expects \ followed by text
sed: stdout: Broken pipe

Missing header fix:  complex.h

There were fixinclude test FAILURES

-----------
Otherwise the summary is this:

         === gcc Summary ===

# of expected passes        62994
# of unexpected failures    49
# of expected failures        211
# of unsupported tests        1606

         === g++ Summary ===

# of expected passes        25521
# of expected failures        160
# of unsupported tests        365

         === libstdc++ Summary ===

# of expected passes        6984
# of expected failures        81
# of unsupported tests        661

         === libgomp Summary ===

# of expected passes        1025
# of unsupported tests        2


On 28.03.11 19:58, Mike Stump - mikestump@comcast.net wrote:
> On Mar 27, 2011, at 8:55 PM, Christian Schüler wrote:
>> please review the following patch (and besides, bear with me as this is the
>> first patch proposal from me). For gcc 4.5 and earlier it was possible to
>> configure xcode via a modified xcplugin to use the newer gcc directly (yes,
>> the -arch flag was ignored during link time, but since I had -m32/-m64
>> anyways, this didn't matter). With the new argument checking of version 4.6
>> during the linking stage this is no longer possible. The proposed patch makes
>> gcc on darwin recognize the -arch flag to the extent necessary to reinstate
>> the old functionality. Besides, it fixes the already existing support for the
>> -F flag.
> Ok (when regression tested).  Did you run the gcc regression testsuite on it?  To install it, we'd need a testsuite run on it.  Roughy, run the testsuite before your patch, save off the .sum file, run it after your patch, then run contrib/compare_tests before.sum after.sum and see if there is any output.  You might need expect/tcl/dejagnu installed to do that.
>
>
>
> If you want to contribute longer term (larger patches), you'll want to get started on your paper work, if you've not done that already.  And, welcome.  Before you say, but...  let me say, what took so long, 10 years is a long while?  :-)
>