On Thu, Apr 30, 2009 at 11:39, Janis Johnson wrote:
Thanks to Janis, Andrew, and David.
I see inside the script all you say, but it seems to be throwing up on
some ill-formed screen output from some of the tests, e.g.,
gawk: cmd. line:50: { next; }
gawk: cmd. line:50: ^ `next' used in E
On Thu, 2009-04-30 at 11:56 -0400, David Fang wrote:
> > On Thu, Apr 30, 2009 at 7:30 AM, Tom Browder wrote:
> >> On Wed, Apr 29, 2009 at 18:28, Janis Johnson wrote:
> >> ...
> >>> The preferred way to post test results is by running the script
> >>> $SRC/contrib/test_summary from within the buil
On Thu, Apr 30, 2009 at 7:30 AM, Tom Browder wrote:
On Wed, Apr 29, 2009 at 18:28, Janis Johnson wrote:
...
The preferred way to post test results is by running the script
$SRC/contrib/test_summary from within the build directory. It
produces a summary in the form of a script which will mail
On Thu, Apr 30, 2009 at 7:30 AM, Tom Browder wrote:
> On Wed, Apr 29, 2009 at 18:28, Janis Johnson wrote:
> ...
>> The preferred way to post test results is by running the script
>> $SRC/contrib/test_summary from within the build directory. It
>> produces a summary in the form of a script which
On Wed, Apr 29, 2009 at 18:28, Janis Johnson wrote:
...
> The preferred way to post test results is by running the script
> $SRC/contrib/test_summary from within the build directory. It
> produces a summary in the form of a script which will mail that
> summary to gcc-testresu...@gcc.gnu.org, whe
On Wed, 2009-04-29 at 08:56 -0500, Tom Browder wrote:
> Attached is a shortened test report with the following lines removed:
>
> XFAIL
> PASS
> UNSUPPORTED
The preferred way to post test results is by running the script
$SRC/contrib/test_summary from within the build directory. It
produces a su
On Wed, Apr 29, 2009 at 9:29 AM, Dennis Clarke wrote:
>
>> Attached is a shortened test report with the following lines removed:
>>
>
> excellent, now we have a benchmark/comparison to look at. Well done,
> excellent work.
>
> What did you use to build libgmp and mpfr ? I am curious because most
>
> Attached is a shortened test report with the following lines removed:
>
excellent, now we have a benchmark/comparison to look at. Well done,
excellent work.
What did you use to build libgmp and mpfr ? I am curious because most
people that try wwith Sun Studio Express or Sun Studio 12 fail pret
> On Sat, Apr 25, 2009 at 9:55 PM, Dennis Clarke
> wrote:
> ...
well done, do you have a full testsuite report ?
>
> Well, Dennis, I have problems running the testsuite. I think I'm
> missing some of the prereqs, so it will be a while. I'll report back
> unless someone finishes first..
I
On Sat, Apr 25, 2009 at 9:55 PM, Dennis Clarke wrote:
...
>>> well done, do you have a full testsuite report ?
Well, Dennis, I have problems running the testsuite. I think I'm
missing some of the prereqs, so it will be a while. I'll report back
unless someone finishes first..
-Tom
> On Sat, Apr 25, 2009 at 9:09 PM, Dennis Clarke
> wrote:
>>
>>> A successful build on Open Solaris 2008.11:
>>>
>>> $../gcc-4.4.0/config.guess
>>> i386-pc-solaris2.11
>>>
>>> $ gcc-4.4.0t -v
>>> Using built-in specs.
>>> Target: i386-pc-solaris2.11
>>> Configured with: ../gcc-4.4.0/configure
>>>
On Sat, Apr 25, 2009 at 9:09 PM, Dennis Clarke wrote:
>
>> A successful build on Open Solaris 2008.11:
>>
>> $../gcc-4.4.0/config.guess
>> i386-pc-solaris2.11
>>
>> $ gcc-4.4.0t -v
>> Using built-in specs.
>> Target: i386-pc-solaris2.11
>> Configured with: ../gcc-4.4.0/configure
>> --enable-langua
> A successful build on Open Solaris 2008.11:
>
> $../gcc-4.4.0/config.guess
> i386-pc-solaris2.11
>
> $ gcc-4.4.0t -v
> Using built-in specs.
> Target: i386-pc-solaris2.11
> Configured with: ../gcc-4.4.0/configure
> --enable-languages=c,c++,fortran --disable-multilib
> --program-suffix=-4.4.0t --
13 matches
Mail list logo
