I have successfully built GCC-4.2.0-20070501 on latest Cygwin snapshot
20070427.
GCC 4.2.0 RC3 is available from:
ftp://gcc.gnu.org/pub/gcc/prerelease-4.2.0-20070501
I have not done run the testsuite ( make check) but have built LLVM and
LLVM-GCC4. So indications are very good.
Aaron
David Daney wrote:
David Daney wrote:
Kaz Kojima wrote:
Hi,
I've noticed that some libjava tests fail for SH on trunk and
4.2.0 RC3.
New tests that FAIL:
Divide_1 -O3 -findirect-dispatch output - bytecode->native test
Divide_1 -O3 output - bytecode->native test
Divide_1 -O3 output - source c
Hello. I have a question regarding the svn logs that get sent to the
gcc-cvs mailing list on every commit. I was wondering if it would be
possible for those mails that contain a PR number to also include the
title of that PR (ie. the contents of in bugzilla). This
would allow people to find the
David Daney wrote:
Kaz Kojima wrote:
Hi,
I've noticed that some libjava tests fail for SH on trunk and
4.2.0 RC3.
New tests that FAIL:
Divide_1 -O3 -findirect-dispatch output - bytecode->native test
Divide_1 -O3 output - bytecode->native test
Divide_1 -O3 output - source compiled test
Divide_
Kaz Kojima wrote:
Hi,
I've noticed that some libjava tests fail for SH on trunk and
4.2.0 RC3.
New tests that FAIL:
Divide_1 -O3 -findirect-dispatch output - bytecode->native test
Divide_1 -O3 output - bytecode->native test
Divide_1 -O3 output - source compiled test
Divide_1 -findirect-dispatc
Hi,
I've noticed that some libjava tests fail for SH on trunk and
4.2.0 RC3.
New tests that FAIL:
Divide_1 -O3 -findirect-dispatch output - bytecode->native test
Divide_1 -O3 output - bytecode->native test
Divide_1 -O3 output - source compiled test
Divide_1 -findirect-dispatch output - bytecode-
On Tue, May 01, 2007 at 11:45:57PM +0200, Rask Ingemann Lambertsen wrote:
>
> $ ./xgcc -B./ ~/cvssrc/gcc/gcc/testsuite/gcc.dg/20020210-1.c \
> -O2 -sim=linuxvm86 -o /tmp/20020210-1-fp -fno-omit-frame-pointer
> $ /tmp/20020210-1-fp; echo $?
> 0
>
> $ ./xgcc -B./ ~/cvssrc/gcc/gcc/testsuite/gcc.dg/2
Richard Guenther wrote:
> 2007-05-05 Richard Guenther <[EMAIL PROTECTED]>
>
>* doc/install.texi (--disable-stage1-checking): Document.
> [EMAIL PROTECTED] --disable-stage1-checking
> [EMAIL PROTECTED] [EMAIL PROTECTED]
> +Regardless of what is specified with @samp{--enable-checking} th
On 5/5/07, Richard Guenther <[EMAIL PROTECTED]> wrote:
On 5/5/07, Richard Guenther <[EMAIL PROTECTED]> wrote:
> On 5/5/07, Mark Mitchell <[EMAIL PROTECTED]> wrote:
> > Richard Guenther wrote:
> >
> > >> > Another problem is that --enable-checking hasn't been set to 'release',
> > >> > so the stag
On 5/5/07, Richard Guenther <[EMAIL PROTECTED]> wrote:
On 5/5/07, Mark Mitchell <[EMAIL PROTECTED]> wrote:
> Richard Guenther wrote:
>
> >> > Another problem is that --enable-checking hasn't been set to 'release',
> >> > so the stage1 binary is too big to run on my ARM systems (and the
> >> > com
On 5/5/07, Mark Mitchell <[EMAIL PROTECTED]> wrote:
Richard Guenther wrote:
>> > Another problem is that --enable-checking hasn't been set to 'release',
>> > so the stage1 binary is too big to run on my ARM systems (and the
>> > compiler will be unnecessarily slower than it needs to be).
>> Are
Richard Guenther wrote:
>> > Another problem is that --enable-checking hasn't been set to 'release',
>> > so the stage1 binary is too big to run on my ARM systems (and the
>> > compiler will be unnecessarily slower than it needs to be).
>> Are you sure that we're not building with release-checkin
On 5/5/07, Mark Mitchell <[EMAIL PROTECTED]> wrote:
Richard Earnshaw wrote:
>> Mark Mitchell wrote:
>>> GCC 4.2.0 RC3 is now available from:
>>>
>>> ftp://gcc.gnu.org/pub/gcc/prerelease-4.2.0-20070501
>>>
>>> This build now contains the fixes for the Ada build problem present in RC2.
>>>
>>> At
Richard Earnshaw wrote:
>> Mark Mitchell wrote:
>>> GCC 4.2.0 RC3 is now available from:
>>>
>>> ftp://gcc.gnu.org/pub/gcc/prerelease-4.2.0-20070501
>>>
>>> This build now contains the fixes for the Ada build problem present in RC2.
>>>
>>> At this point, I have no plans for an RC4. However, I a
GCC 4.2.0 RC3 is now available from:
ftp://gcc.gnu.org/pub/gcc/prerelease-4.2.0-20070501
It does not build LLVM there seems to be a stdlib++ problem.
I cannot really file a BugZilla report as I have not distilled the code
down to make an accurate report.
Luckily it was just a local library
See PR31095.
Thanks, Daniel.
Paul
On Saturday 05 May 2007 17:57:30 Paul Richard Thomas wrote:
> This has appeared in recent days, with any level of optimization other
> than none at all.
>
> [EMAIL PROTECTED] prs]# /svn-4.3/bin/gfortran -static -O1
> $test/../gfortran.fortran-torture/execute/st_function.f90
> /svn/trunk/gcc/testsui
This has appeared in recent days, with any level of optimization other
than none at all.
[EMAIL PROTECTED] prs]# /svn-4.3/bin/gfortran -static -O1
$test/../gfortran.fortran-torture/execute/st_function.f90
/svn/trunk/gcc/testsuite/gfortran.dg/../gfortran.fortran-torture/execute/st_function.f90:
In
Quoting Tom Tromey <[EMAIL PROTECTED]>:
"Antoine" == Antoine Eiche <[EMAIL PROTECTED]> writes:
Without more information I don't know how to answer your question.
But I do have a question for you...
Antoine> I must calculate the address of an element's array.
Antoine> If the size of an element
> > m68k does too, just nobody uses it any more or the ones they use don't
> > have the co-processor or have a different FP instructions now. In
> > fact this where the problem started, i387 just continued in the same
> > fashion.
>
> Huh? m68k still uses extended precisions and will continue to d
20 matches
Mail list logo
