Re: (new) Failure building GFortran (Cygwin)

2008-07-07 Thread Ian Lance Taylor
Angelo Graziosi <[EMAIL PROTECTED]> writes: > --- gcc-4.4-20080704.orig/gcc/ggc-page.c 2008-06-29 06:39:16.0 +0200 > +++ gcc-4.4-20080704/gcc/ggc-page.c 2008-07-05 12:00:20.90625 +0200 > @@ -799,7 +799,7 @@ > alloc_size = GGC_QUIRE_SIZE * G.pagesize; >else > alloc_s

Re: (new) Failure building GFortran (Cygwin)

2008-07-07 Thread Kaveh R. GHAZI
On Tue, 8 Jul 2008, Angelo Graziosi wrote: > --- gcc-4.4-20080704.orig/gcc/ggc-page.c 2008-06-29 06:39:16.0 +0200 > +++ gcc-4.4-20080704/gcc/ggc-page.c 2008-07-05 12:00:20.90625 +0200 > @@ -799,7 +799,7 @@ > alloc_size = GGC_QUIRE_SIZE * G.pagesize; > else > alloc_s

Re: (new) Failure building GFortran (Cygwin)

2008-07-07 Thread Angelo Graziosi
Ian Lance Taylor ha scritto: Angelo Graziosi <[EMAIL PROTECTED]> writes: Ian Lance Taylor wrote: It's valid, but it's not the right patch. The right patch is to use XNEW and XCNEW from include/libiberty.h. Gabriel Dos Reis in [1] wrote: The idiom is to use XCNEWVAR(T) for xcalloc(1, sizeo

Re: (new) Failure building GFortran (Cygwin)

2008-07-07 Thread Ian Lance Taylor
Angelo Graziosi <[EMAIL PROTECTED]> writes: > Ian Lance Taylor wrote: >> It's valid, but it's not the right patch. The right patch is to use >> XNEW and XCNEW from include/libiberty.h. >> > > Gabriel Dos Reis in [1] wrote: >> The idiom is to use XCNEWVAR(T) for xcalloc(1, sizeof(T)), >> XNEWVAR(

Re: (new) Failure building GFortran (Cygwin)

2008-07-07 Thread Angelo Graziosi
Ian Lance Taylor wrote: It's valid, but it's not the right patch. The right patch is to use XNEW and XCNEW from include/libiberty.h. Gabriel Dos Reis in [1] wrote: > The idiom is to use XCNEWVAR(T) for xcalloc(1, sizeof(T)), > XNEWVAR(T) for xmalloc(sizeof(T)),... Gulp! I am a little confu

Re: GNU LD fails to generate correct ARM Thumb veneer

2008-07-07 Thread Aaron P. D'Souza
hello Nick: thank you for your prompt response. i have seen your crt0.S. - the first file to be linked is an ARM assembly .s file that contains the ARM vector table and handler addresses. the vector table is in a separate section called .VhaInit. Did you know that you can use the KEEP dir

Re: Trouble with gdb 6.8 on Irix

2008-07-07 Thread Joseph S. Myers
On Mon, 7 Jul 2008, Joel Brobecker wrote: > > If you care about GDB on mips-irix, I strongly advise caring about GCC as > > well, or finding someone to care about it. Right now, it is on the list > > of targets to be deprecated in GCC 4.4 because we wish to remove fixproto > > and it is one of

Re: (new) Failure building GFortran (Cygwin)

2008-07-07 Thread Ian Lance Taylor
Angelo Graziosi <[EMAIL PROTECTED]> writes: > Could this be valid? It's valid, but it's not the right patch. The right patch is to use XNEW and XCNEW from include/libiberty.h. Ian

Re: GNU LD fails to generate correct ARM Thumb veneer

2008-07-07 Thread Nick Clifton
Hi Aaron, - the first file to be linked is an ARM assembly .s file that contains the ARM vector table and handler addresses. the vector table is in a separate section called .VhaInit. Did you know that you can use the KEEP directive in a linker script (or a linker script fragment) i

Re: Trouble with gdb 6.8 on Irix

2008-07-07 Thread Joel Brobecker
[moved to the GCC list] > > I think that GDB on mips-irix has been in dire need of attention. > > It's something I have on my list and I hope to get to it by the end > > of the year, but my hopes often get overridden by more urgent issues... > > The release that AdaCore uses in its product is GDB

GNU LD fails to generate correct ARM Thumb veneer

2008-07-07 Thread Aaron P. D'Souza
good day people: i have been using GNUARM/Cygwin for some time now and i have not encountered a problem like this before. BACKGROUND - target MCU is STR71x - CPU core is ARM7TDMI - toolchain is GNUARM 4.1.1 on Cygwin - source code - the first file to be linked is an ARM assembly .s file th

Re: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats

2008-07-07 Thread Gabriel Dos Reis
On Mon, Jul 7, 2008 at 4:48 AM, Dave Korn <[EMAIL PROTECTED]> wrote: > Kaveh R. GHAZI wrote on 06 July 2008 23:36: > >> * gcc.c (execute): Fix -Wc++-compat warning. > > > Kaveh, am I right in inferring from recent list traffic that you've taken > on a whole load of c-vs-c++ compatibility wor

RE: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats

2008-07-07 Thread Dave Korn
Kaveh R. GHAZI wrote on 06 July 2008 23:36: > * gcc.c (execute): Fix -Wc++-compat warning. Kaveh, am I right in inferring from recent list traffic that you've taken on a whole load of c-vs-c++ compatibility work? If so, have you seen / can you take a look at http://gcc.gnu.org/ml/gcc/20

If you look stupid in bed

2008-07-07 Thread revd
Your new source of great health. http://oj.doctorfeelgoodphd.eu

Re: (new) Failure building GFortran (Cygwin)

2008-07-07 Thread Angelo Graziosi
Dave Korn ha scritto: Angelo Graziosi wrote on 05 July 2008 12:16: For the sake of completeness I want to flag that the current snapshot 4.4-20080704 has new failures: /work/gcc/gcc/ggc-page.c -o ggc-page.o cc1: warnings being treated as errors /work/gcc/gcc/ggc-page.c: In function 'alloc_pa