Re: GCC Compiler Engineer job (I am not a recruiter)

2006-04-12 Thread Mark Mitchell
Gerald Pfeifer wrote: > On Mon, 10 Apr 2006, Mark Mitchell wrote: >> It seems like we're getting consensus around that approach, despite the >> initial sentiment in the other direction from Mike and Joe. Mike, Joe, >> do either of you care to argue the point? If not, I'll volunteer to >> write so

Problem in function in-lining

2006-04-12 Thread Ching-Hua Chang
We had ported gcc-3.4.2 to our own RISC, and meet a strange case in optimization level 3 (-O3). The compiler produce wrong assembly code in O3 and correct result if we add -fno-inline flag. It seems that there some problem in function in-lining. What can I do and what should I do to solve this pr

Question about gcc-lib and building on SPARC

2006-04-12 Thread Mark Cuss
Hello - this is definitely a newbie question, so bear with me... We've been using gcc under Solaris on SPARC hardware for some time now. The guy who was here before me set up the previous version (gcc-3.3.3) and now I'm trying to get gcc-3.4.4 to build. In the old gcc-3.3.3 install tree, I h

[Ada] multilibbed implementation?

2006-04-12 Thread Christian Joensson
It's that time again... I just want to ask if there's any progress on Ada being multilibbed? -- Cheers, /ChJ

Catching up on status reports

2006-04-12 Thread Mark Mitchell
I'm behind on two RM duties: bug priorities and status reports. Fortunately, I'm not traveling this week, so I'll get caught up shortly. I just wanted to let everyone know that I'd not forgotten there's stuff to be done... Thanks, -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x

Re: R_PPC_REL24 overflow

2006-04-12 Thread James Lemke
I suppose I should summarize what this problem was in case it's useful to anyone else searching the archives. A buggy cross-build process did not create libc.so. The static linker didn't find libc.so so it silently used libc.a instead. Libc.a is not built with -fPIC so the load problem showed up.

[gomp] EH problems with OpenMP

2006-04-12 Thread Volker Reichelt
Hi, OpenMP is currently more or less unusable with the C++ front-end because of EH issues (see PR26823). This unfortunate situation is dragging on for more than two months now and makes further testing impossible. Some of the problems were fixed in PR26084, some still remain: The original (unredu

RE: Reloading Problems and Memory Addressing

2006-04-12 Thread Dave Korn
On 12 April 2006 06:48, Frank Riese wrote: > Yes, you're right. When I started writing this backend I didn't have much > experience with it. I took the smallest backend I could find and tried to > adjust it to me needs. The number of macros in the internals docs was a bit > overwhelming at first a

Re: Reloading Problems and Memory Addressing

2006-04-12 Thread Rask Ingemann Lambertsen
On Wed, Apr 12, 2006 at 07:47:32AM +0200, Frank Riese wrote: > On Monday 10 April 2006 19:48, you wrote: > > Can it at least add (small) immediates to registers? > > Nope, sry. The only instructions that take other arguments than registers are > the aforementioned LDL/LDH (load low/high), branch

RE: Question about build error

2006-04-12 Thread Dave Korn
On 12 April 2006 10:14, Eric Fisher wrote: > hi, > When I build gcc-3.2.2 for mips target, there's an error. What's the > problem? > > Thanks > Eirc > > ake[1]: Leaving directory `/home/cii/qwang_gcc/libiberty' > xgcc: specs file malformed after 4096 characters > xgcc: specs file malformed afte

Question about build error

2006-04-12 Thread Eric Fisher
hi, When I build gcc-3.2.2 for mips target, there's an error. What's the problem? Thanks Eirc ake[1]: Leaving directory `/home/cii/qwang_gcc/libiberty' xgcc: specs file malformed after 4096 characters xgcc: specs file malformed after 4096 characters xgcc: specs file malformed after 4096 character

Re: i read that i should send here email

2006-04-12 Thread Paolo Bonzini
Piotr Marasz wrote: I try compile example program gcc.exe -I"c:\gcc\include" -L"c:\gcc\lib" c:\gcc\bin\program.c gcc.exe: Internal error: (null) (program as) Please submit bug report. First the bug report should not go here but to http://gcc.gnu.org/bugzilla (this is a list for development of