Re: Several puzzles about gcc top level makefile

2008-11-29 Thread Cheng bin
Thanks very much, Ian Lance Taylor . I will go deeper into the makefiles.

Re: CSE bug when narrowing constants

2008-11-29 Thread Eric Botcazou
> The conditional jump instruction formed by instructions > 56 and 57 above is deleted because GCSE thinks that > (reg:SI 61 [ p$thread ]) is non-zero. It comes to this > conclusion when it propagates the >REG_EQUAL (const_int 4294967296 [0x1]) > value listed in instruction 25: > > (in

Re: Functional Purity

2008-11-29 Thread Andrew Haley
Brendon Costa wrote: > I want to use GCC to categorise "functional purity" in C++. My > definition will differ from classic functional purity. In particular: > > A function is considered pure if it makes no changes to existing > memory or program state. There may be a few exceptions to this rule

Re: Functional Purity

2008-11-29 Thread Eric Botcazou
> The reason for posting this is to ask. Is there code in GCC that > already does something "similar" in say one of the optimisation passes > so i can get a look at how to get started on this? ipa-pure-const.c -- Eric Botcazou

Proposal : Implement SEH exceptions into [ce]gcc

2008-11-29 Thread mosfet
Hi, I am working on mobile CE devices and I use cegcc (when it's possible) to developp software. There is one feature I miss with gcc called SEH exceptions and since I have seen a recent post about SEH x64 I think it's the right moment to talk about it. First SEH exceptions exists in two kinds :

Re: CSE bug when narrowing constants

2008-11-29 Thread Gary Funck
On 11/29/08 10:37:33, Eric Botcazou wrote: > > The conditional jump instruction formed by instructions > > 56 and 57 above is deleted because GCSE thinks that > > (reg:SI 61 [ p$thread ]) is non-zero. It comes to this > > conclusion when it propagates the > >REG_EQUAL (const_int 4294967296 [0x

Re: CSE bug when narrowing constants

2008-11-29 Thread Eric Botcazou
> Agreed. The routine that creates the errant REG_EQUAL note is > lookup_as_function(). Really? Doesn't it only retrieve a pre-existing REG_EQUAL note? -- Eric Botcazou

Re: CSE bug when narrowing constants

2008-11-29 Thread Gary Funck
On 11/29/08 14:45:49, Eric Botcazou wrote: > > Agreed. The routine that creates the errant REG_EQUAL note is > > lookup_as_function(). > > Really? Doesn't it only retrieve a pre-existing REG_EQUAL note? It retrieves an equivalent rtx constant, if it exists. Before the patch, the constant that

Supporting IEEE 754 [exceptions] (in a front end [gfortran])

2008-11-29 Thread Tobias Burnus
Hello, I'm thinking about how to implement Fortran 2003's IEEE support in gfortran. The IEEE allow a) To set an IEEE value (NaN, INF, etc.) b) Check whether a value is NaN, etc. c) To query for IEEE capabilities (IEEE_SUPPORT_NAN, IEEE_SUPPORT_SQRT (a sqrt() which has IEEE exception support), etc.

Re: Supporting IEEE 754 [exceptions] (in a front end [gfortran])

2008-11-29 Thread Steve Kargl
On Sat, Nov 29, 2008 at 09:41:30PM +0100, Tobias Burnus wrote: > > I'm thinking about how to implement Fortran 2003's IEEE support in > gfortran. The IEEE allow > a) To set an IEEE value (NaN, INF, etc.) > b) Check whether a value is NaN, etc. > c) To query for IEEE capabilities (IEEE_SUPPORT_NAN,

Re: Supporting IEEE 754 [exceptions] (in a front end [gfortran])

2008-11-29 Thread Joseph S. Myers
On Sat, 29 Nov 2008, Tobias Burnus wrote: > While (a) and (b) can be easily handled in the front end, I don't see > how I can handle the rest efficiently. Most parts are provided by > fenv.h, for which I seemingly have to write a wrapper function (in > libgfortran) as the typedefs and constants ca

Re: Supporting IEEE 754 [exceptions] (in a front end [gfortran])

2008-11-29 Thread Tobias Burnus
Joseph S. Myers wrote: >> My biggest issue is that I don't see how I can compile-time evaluate the >> following - or how to evaluate it at all: >> >> if (IEEE_SUPPORT_NAN(x)) &! should be always true (or false) on a >> given system >> > See MODE_HAS_NANS etc. in real.h > Thanks. There I

Fwd: Functional Purity

2008-11-29 Thread Brendon Costa
Forgot to reply all... -- Forwarded message -- From: Brendon Costa <[EMAIL PROTECTED]> Date: 2008/11/30 Subject: Re: Functional Purity To: David Fang <[EMAIL PROTECTED]> >Sounds like you want to (at least): > > 1) automatically qualify every declaration (including paramet

gcc4.1.2 compilation errors

2008-11-29 Thread yx
Hi, I am trying to compile SPEC2000 benchmark with gcc 4.1.2 (gfortran and g++ were compiled successfully for gcc4.1.2.) However I got compilation errors for 4 benchmarks in SPEC2000. The error messages are listed as follows: 176. gcc: reorg.c: In function 'find_end_label' reorg.c:831: error: inv

Re: gcc4.1.2 compilation errors

2008-11-29 Thread Andrew Thomas Pinski
Sent from my iPhone On Nov 29, 2008, at 6:34 PM, yx <[EMAIL PROTECTED]> wrote: Hi, I am trying to compile SPEC2000 benchmark with gcc 4.1.2 (gfortran and g++ were compiled successfully for gcc4.1.2.) However I got compilation errors for 4 benchmarks in SPEC2000. The error messages are listed

optimization removes a __builtin_memcpy?

2008-11-29 Thread Steve Kargl
First, I'll preface this with "I'm probably doing something wrong." I'm adding support to gfortran for the ERRMSG argument to [DE]ALLOCATE. Here's, some code to demonstrate: program a call works call fails end program a ! ! Work with all optimization levels. ! subroutine works character(l