Re: gccgo language contribution accepted

2010-01-30 Thread Ian Lance Taylor
Mark Wielaard writes: > On Thu, Jan 28, 2010 at 10:03:04AM -0800, Ian Lance Taylor wrote: >> "Joseph S. Myers" writes: >> > What has been decided about copyright assignment requirements? >> >> This is the general plan as I understand it. >> >> I will separate the gcc-specific parts from the re

Re: Support for export keyword to use with C++ templates ?

2010-01-30 Thread Dodji Seketeli
On Sat, Jan 30, 2010 at 01:47:03AM +0200, Timothy Madden wrote: > So nobody here wants to try a big thing ? :( This question strikes me as being not very fair because many GCC people are already pretty much involved. Would you fancy giving a hand? > How long would it take for someone to understa

Re: gccgo language contribution accepted

2010-01-30 Thread Mark Wielaard
On Thu, Jan 28, 2010 at 10:03:04AM -0800, Ian Lance Taylor wrote: > "Joseph S. Myers" writes: > > What has been decided about copyright assignment requirements? > > This is the general plan as I understand it. > > I will separate the gcc-specific parts from the rest of the Go > frontend. Those

Re: Support for export keyword to use with C++ templates ?

2010-01-30 Thread Ian Lance Taylor
Paolo Carlini writes: > Anyway, modulo a possible deprecation (I believe M$ through Herb is > still pushing for it) I think the slightly more serious side of this > export thing is something Mark, if I'm not mistaken, said some time > ago, at the very beginning of the Lto ideas, to the effect th

Re: Register allocation and multi-reg HARD_FRAME_POINTER

2010-01-30 Thread Ian Lance Taylor
Uros Bizjak writes: > The target that I would like to support has 8-bit registers, so for > any sane compilation, stack pointer, frame pointer and hard frame > pointer all need to be constructed from at least two registers, to > form 16-bit register pair {rA, rB}. > > The stack pointer is defined

Re: Question about reworking internals manual

2010-01-30 Thread Ian Lance Taylor
Jerry Quinn writes: > I'm looking at reworking the sections on trees in the internals manual > and had a question about how to proceed. Right now, the information is > spread between the GENERIC chapter and Trees chapter. The Trees chapter > interleaves a lot of C and C++-specific info in with

Re: Support for export keyword to use with C++ templates ?

2010-01-30 Thread Paolo Carlini
Hi I already tried to tell him that upthread. Sorry about that, last night was tired and didn't follow the whole thread. Anyway, modulo a possible deprecation (I believe M$ through Herb is still pushing for it) I think the slightly more serious side of this export thing is something Ma

Register allocation and multi-reg HARD_FRAME_POINTER

2010-01-30 Thread Uros Bizjak
Hello! The target that I would like to support has 8-bit registers, so for any sane compilation, stack pointer, frame pointer and hard frame pointer all need to be constructed from at least two registers, to form 16-bit register pair {rA, rB}. The stack pointer is defined as a fixed register

Question about reworking internals manual

2010-01-30 Thread Jerry Quinn
Hi, folks. I'm looking at reworking the sections on trees in the internals manual and had a question about how to proceed. Right now, the information is spread between the GENERIC chapter and Trees chapter. The Trees chapter interleaves a lot of C and C++-specific info in with GENERIC info. Wha

Re: Obsoleting IRIX < 6.5, Solaris 7, and Tru64 UNIX < V5.1

2010-01-30 Thread Daniel Jacobowitz
On Sat, Jan 30, 2010 at 07:28:01AM -0800, Ian Lance Taylor wrote: > However, it would not surprise me to discover that there are embedded > systems out there still using o32, with assembly functions which > expect the o32 calling convention. I would be cautious about removing > support for o32 ent

Re: Obsoleting IRIX < 6.5, Solaris 7, and Tru64 UNIX < V5.1

2010-01-30 Thread Richard Guenther
On Sat, Jan 30, 2010 at 4:28 PM, Ian Lance Taylor wrote: > Richard Sandiford writes: > >>> ** I also consider obsoleting support for the O32 ABI: the SGI linker used >>>    is different from the N32/N64 ld, and has repeatedly caused problems >>>    which couldn't be resolved even when SGI still h

Re: Obsoleting IRIX < 6.5, Solaris 7, and Tru64 UNIX < V5.1

2010-01-30 Thread Ian Lance Taylor
Richard Sandiford writes: >> ** I also consider obsoleting support for the O32 ABI: the SGI linker used >>is different from the N32/N64 ld, and has repeatedly caused problems >>which couldn't be resolved even when SGI still had full IRIX >>support. Also, the ISO C99 support in libc i

gcc version 4.4.3 (GCC)

2010-01-30 Thread Wolfgang Griech
config.guess: i686-pc-linux-gnu gcc --v: Using built-in specs. Target: i686-pc-linux-gnu Configured with: ./configure Thread model: posix gcc version 4.4.3 (GCC) packages: gcc-4.4.3.tar.bz2 gcc-core-4.4.3.tar.bz2 gcc-g++-4.4.3.tar.bz2 linux distribution: Ubuntu 8.04.4 LTS \n \l kernel version:

Re: Obsoleting IRIX < 6.5, Solaris 7, and Tru64 UNIX < V5.1

2010-01-30 Thread Richard Sandiford
Rainer Orth writes: > * IRIX before 6.5: > > ** IRIX 5.3 entered retired mode by the end of 1998. Patches are no >longer available from support.sgi.com, and a full bootstrap and test >cycle takes 8 1/2 days on the machines I have available, even without >java/libgcj. > > ** IRIX 6.2