Re: relation between gcc/glibc version and linux kernel version??

2007-06-24 Thread Tim Prince
[EMAIL PROTECTED] wrote: How closely tied are the linux kernel version and the gcc/glibc versions? and where exactly does binutils come in? Not at all closely, although versions from different years are unlikely to be well tested together. For eg: can i run a system with linux-2.4.20 kernel

Re: relation between gcc/glibc version and linux kernel version??

2007-06-24 Thread Mike Stump
On Jun 24, 2007, at 9:32 PM, ganesh subramonian wrote: I have a very basic doubt regarding gcc,binutils and kernel. How closely tied are the linux kernel version and the gcc/glibc versions? Versions of gcc are never (much) dependent on kernel versions. They are rarely dependent on glibc ve

relation between gcc/glibc version and linux kernel version??

2007-06-24 Thread ganesh subramonian
Hi I have a very basic doubt regarding gcc,binutils and kernel. How closely tied are the linux kernel version and the gcc/glibc versions? and where exactly does binutils come in? What kind of changes usually require that version x of kernel requires version y of binutils and gcc-z. And is there

Re: old intentional gcc bug?

2007-06-24 Thread Eric Botcazou
> Indeed. It would be interesting to confirm whether or not a copy of gcc > bootstrapped with a non-gcc compiler matched byte-for-byte with a copy > of gcc bootstrapped from gcc. I just made the experiment on an old SPARC/Solaris 2.5.1 machine and they differ (cc is Sun C 5.0 and gcc is GCC 3.4.

Re: old intentional gcc bug?

2007-06-24 Thread Mike Stump
On Jun 23, 2007, at 2:38 PM, Robert Dewar wrote: On the contrary, since gcc can always be built using third party C compilers, it would be much easier to smoke out and eliminate any such behavior (indeed this example shows the merit of maintaining the property that gcc can be compiled by non

Re: Bootstrap comparison failure on powerpc64 for Ada

2007-06-24 Thread Revital1 Eres
[EMAIL PROTECTED] wrote on 24/06/2007 01:17:34: > > I tested it on powerpc64-linux with the default option > > --with-cpu=default32. > > Ah, so this is a 32-bit compiler like on sparc64-linux? --with-cpu=default32 means that the compiler itself and it's produced code are 32 bits by default. Re