gcc-4.1-20060728 is now available

2006-07-28 Thread gccadmin
Snapshot gcc-4.1-20060728 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20060728/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.1 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

converting a CALL_EXPR node without any argument into SSA form, thanks

2006-07-28 Thread sean yang
I asked the question about the name compatibility for CALL_EXPR in SSA form. Thanks for the answers from this mailing list. My understanding is that we don't need to convert a stmt node into SSA form as long as the call instruction (CALL_EXPR) does not use any variable as an argument. But the

Re: Suggestion required for appropriate implementation

2006-07-28 Thread Ian Lance Taylor
"Rahul Phalak" <[EMAIL PROTECTED]> writes: > According to the first syntax, Wanalyze-Rule1, Wanalyze-Rule2 etc are > considered as seperate options in c.opt file. Look at Joined options. Consider -fbuiltin-abs -fno-builtin-memcpy. Ian

Re: _LARGE_FILES support in AIX -GCC compilation problem.

2006-07-28 Thread David Edelsohn
This is related to PR 20366. One needs to build the libraries and header files with -D_LARGE_FILE enabled, but this causes some conflicts which have not been resolved yet. David

Re: gcc-4.3 projects page?

2006-07-28 Thread Mark Mitchell
Dan Kegel wrote: > Is it time to create a GCC_4.3_Projects page > like http://gcc.gnu.org/wiki/GCC_4.2_Projects ? > I imagine several projects are already in progress, > but not yet mentioned on the wiki... Yes, I've been thinking about doing that. It's fine with me if someone would like to creat

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Daniel Jacobowitz
On Fri, Jul 28, 2006 at 11:44:12AM +0200, Jan Hubicka wrote: > Interesting, the major reason for disabling -m64 by default for 32bit > compilers was the fact that it enforces HOST_WIDE_INT to be 64bit > slowing down the whole compiler considerably. Are Debian's folks happy > to wait longer for com

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Andrew Pinski
On Jul 28, 2006, at 4:47 AM, Richard Guenther wrote: The memory requirement for PR12245 will nearly double. Saying it will double is not prove, please provide the memory usage dumps. If it does double then you should not be using x86 to optimize the memory usage and instead using powerpc-li

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Richard Guenther
On 7/28/06, Andrew Pinski <[EMAIL PROTECTED]> wrote: On Jul 28, 2006, at 3:01 AM, Richard Guenther wrote: > > It also uses more memory due to this change. I still have not seen any real data from this. All I have seen is talk. The memory usage has gone down with the change for RTL and also HO

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Andrew Pinski
On Jul 28, 2006, at 3:01 AM, Richard Guenther wrote: It also uses more memory due to this change. I still have not seen any real data from this. All I have seen is talk. The memory usage has gone down with the change for RTL and also HOST_WIDEST_FAST_INT changes. Please provide evidence th

Re: GCC missed optimization?

2006-07-28 Thread Andrew Pinski
On Jul 28, 2006, at 3:04 AM, Richard Guenther wrote: A bugreport is useful so we don't forget. There is already a bug report. PR 21465. -- Pinski

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Andrew Pinski
On Jul 28, 2006, at 2:44 AM, Jan Hubicka wrote: Interesting, the major reason for disabling -m64 by default for 32bit compilers was the fact that it enforces HOST_WIDE_INT to be 64bit slowing down the whole compiler considerably. Are Debian's folks happy to wait longer for compilation or h

Re: GCC missed optimization?

2006-07-28 Thread Richard Guenther
On 7/28/06, François-Xavier Coudert <[EMAIL PROTECTED]> wrote: I've been doing some benchmarking of gfortran, and reducing the testcase leads to what seems a missed optimization in the following code: $ cat a.c void foo (float * restrict x, float * restrict y) { int i; for (i = 0; i < 1

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Richard Guenther
On 7/28/06, Jan Hubicka <[EMAIL PROTECTED]> wrote: > On Thu, Jul 27, 2006 at 12:56:14PM +0200, Denis Vlasenko wrote: > > does it mean I need a cross-compiler (to x86_64) to use -m64? > > It's strange because then -m64 is not useful at all > > - x86_64 cross compiler defaults to 64 bit anyway... r

GCC missed optimization?

2006-07-28 Thread François-Xavier Coudert
I've been doing some benchmarking of gfortran, and reducing the testcase leads to what seems a missed optimization in the following code: $ cat a.c void foo (float * restrict x, float * restrict y) { int i; for (i = 0; i < 1; i++) x[i] = y[i] * y[i]; } $ gcc a.c -O1 -ffast-math -msse -m

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Jan Hubicka
> On Thu, Jul 27, 2006 at 12:56:14PM +0200, Denis Vlasenko wrote: > > does it mean I need a cross-compiler (to x86_64) to use -m64? > > It's strange because then -m64 is not useful at all > > - x86_64 cross compiler defaults to 64 bit anyway... right? > > It overrides -m32 earlier on the command l

Re: sorry, unimplemented: 64-bit mode not compiled in - ?!

2006-07-28 Thread Denis Vlasenko
On Thursday 27 July 2006 15:44, Daniel Jacobowitz wrote: > On Thu, Jul 27, 2006 at 12:56:14PM +0200, Denis Vlasenko wrote: > > does it mean I need a cross-compiler (to x86_64) to use -m64? > > It's strange because then -m64 is not useful at all > > - x86_64 cross compiler defaults to 64 bit anyway.

RE: Suggestion required for appropriate implementation

2006-07-28 Thread Rahul Phalak
Hi, >>It's a little hard to know the best approach with no idea of what kinds of rules you are talking about. However, given that The rules that I am talking about are the rules that will help user to write efficient code. For e.g. "Declare variables in descending order according to base ty

_LARGE_FILES support in AIX -GCC compilation problem.

2006-07-28 Thread Kithsiri Lekamge
Hi All, I am using GCC 3.46 version for AIX 5.1 platform. I have used the -D_LARGE_FILES -D_LARGE_FILE_API as part of compiler options. Then i received the follwoing error: /opt/gccsrc1/GCC_INSTALL_DIR/lib/gcc/powerpc-ibm-aix5.1.0.0/3.4.6/../../../../include/c++/3.4.6/cstdio:108: error: `::fgetpo