Re: g++ 4.3, troubles with C++ indexing idioms

2007-07-24 Thread Paolo Bonzini
For performance small arrays should be the same as individual members (I can see the annoying fact that initialization is a headache - this has annoyed me as well). For larger arrays (>4 members), aliasing will make a difference possibly, making the array variant slower. Any union variant is e

Re: GCC with formal testing docs

2007-07-24 Thread Ben Elliston
On Tue, 2007-07-24 at 10:48 +0100, Manuel López-Ibáñez wrote: > GCC is thoroughly tested. None the less, there is always room for > improvement, so if you have time to implement your ideas or write > documentation, you are welcome to contribute. If you build the compiler with coverage instrumenta

Rebuild GCC 4.2

2007-07-24 Thread S.SRIDHAR
Hi... Now i am working on GCC v3.3.2 and kernel 2.4,i want to upgrade both to the latest version GCC v4.2 and kernel 2.6,i don't know how to do so can u help me With Warm Regards, S.Sridhar, Mobile: 99406 80274 Phone: 42199573/42100500 Fax :42199502 E- Mail : [EMAIL PROTECTED] ww

Re: g++ 4.3, troubles with C++ indexing idioms

2007-07-24 Thread tbp
On 7/24/07, Richard Guenther <[EMAIL PROTECTED]> wrote: For performance small arrays should be the same as individual members (I can see the annoying fact that initialization is a headache - this has annoyed me as well). For larger arrays (>4 members), aliasing will make a difference possibly, m

Re: debugging info considered harmful to lto.

2007-07-24 Thread Jan Hubicka
> Jan Hubicka wrote: > >Thanks for explanation - the space optimization seems relatively > >chalenging to implement, in particular because the variables in scope > >might change in between the time abstract copy is output and the time > >the block referencing to the block via abstract pointer is ou

Re: debugging info considered harmful to lto.

2007-07-24 Thread Kenneth Zadeck
Jason Merrill wrote: > Jan Hubicka wrote: >> Thanks for explanation - the space optimization seems relatively >> chalenging to implement, in particular because the variables in scope >> might change in between the time abstract copy is output and the time >> the block referencing to the block via a

Re: debugging info considered harmful to lto.

2007-07-24 Thread Jason Merrill
Jan Hubicka wrote: Thanks for explanation - the space optimization seems relatively chalenging to implement, in particular because the variables in scope might change in between the time abstract copy is output and the time the block referencing to the block via abstract pointer is output. The

Re: paranoia on PowerPC

2007-07-24 Thread Joel Sherrill
Joern Rennecke wrote: Given the age of paranoia (the version included with RTEMS is from Cygnus circa 1993), does this sound familiar or is this a new issue? Is this related to PR29100? I don't think so since I was using 4.2.1 and tried that option upon someone else's suggestion. FWIW

Re: bootstrap broken on trunk r126866

2007-07-24 Thread Thomas Koenig
On Tue, 2007-07-24 at 11:23 +0200, Thomas Veith wrote: > Hi *, > > bootstrap is broken on trunk rev. 126866 during Stage3: Thanks. This has been fixed by Tobias Burnus with http://gcc.gnu.org/ml/gcc-cvs/2007-07/msg00736.html .

Re: SH2A: "RTV/N Rn" implementation

2007-07-24 Thread Rask Ingemann Lambertsen
On Tue, Jul 24, 2007 at 03:32:03PM +0530, Naveen H.S. wrote: > > Thanks for your valuable suggestion. > We modified the epilogue as per your suggestions. RTV/N Rn instruction > was generated with the operand as R0 in most of the case. The redundant > transfer of register Rn to R0 before the epi

Re: paranoia on PowerPC

2007-07-24 Thread Joern Rennecke
> Given the age of paranoia (the version included > with RTEMS is from Cygnus circa 1993), does this > sound familiar or is this a new issue? Is this related to PR29100?

inappropriate disclaimers (Was: Re: Installing gcc-3.2)

2007-07-24 Thread Joern Rennecke
> I'd like to strongly encourage contributors to the list to avoid > replying to e-mail which contain these disclaimers. They give the > administrators of gcc.gnu.org a legal liability, since we do not > follow the directions in the disclaimer. It's true that we would > almost certainly win a cou

Re: paranoia on PowerPC

2007-07-24 Thread Joel Sherrill
Tim Prince wrote: [EMAIL PROTECTED] wrote: On Mon, 2007-07-23 at 19:00 -0700, Tim Prince wrote: Should we know which version of Paranoia this is? It's the version having been integrated into the rtems source tree many years ago: http://www.rtems.org/cgi-bin/viewcvs.cgi/rtems/testsuites/sampl

[tuples] Mainline merge (@126872)

2007-07-24 Thread Diego Novillo
The merge was quite messy. For some strange reason, I got hundreds of files with conflicts. Maybe because it had been a long time that we hadn't done a merge. In any case, the merged branch still passes the few gimplification tests we have, so it can't be too broken.

Re: paranoia on PowerPC

2007-07-24 Thread Tim Prince
[EMAIL PROTECTED] wrote: On Mon, 2007-07-23 at 19:00 -0700, Tim Prince wrote: Should we know which version of Paranoia this is? It's the version having been integrated into the rtems source tree many years ago: http://www.rtems.org/cgi-bin/viewcvs.cgi/rtems/testsuites/samples/paranoia/paranoi

Re: g++ 4.3, troubles with C++ indexing idioms

2007-07-24 Thread Richard Guenther
On 7/21/07, tbp <[EMAIL PROTECTED]> wrote: On 7/19/07, Richard Guenther <[EMAIL PROTECTED]> wrote: > Of course, if any then the array indexing variant is fixed. It would be nice > to see a complete testcase with a pessimization, maybe you can file > a bugreport about this? There's many issues fo

RE: GCC with formal testing docs

2007-07-24 Thread Dave Korn
On 24 July 2007 07:42, ?? wrote: > Hi: >I know GCC is a wonderful compiler collection. I like it and trust > it. But, I can't find any formal docs about Testing GCC, both unit > testing and integrat testing. I think, as a software, GCC should be > tested and own a test report. > >Can some

Re: GCC with formal testing docs

2007-07-24 Thread Anitha Boyapati
Hi, >I know GCC is a wonderful compiler collection. I like it and trust > it. That sounds dramatic. Never trust a compiler if you want to test it :) > But, I can't find any formal docs about Testing GCC, both unit > testing and integrat testing. I think, as a software, GCC should be >

RE: SH2A: "RTV/N Rn" implementation

2007-07-24 Thread Naveen H.S.
Hi, >> This is actually what I had in mind. You just need to also modify >> the epilogue expander to use that insn: >> sh_expand_epilogue (0); >> if (HAVE_return_rtv) >>emit_jump_insn (gen_return_rtv (gen_rtx_REG (SImode, R0_REG))); >> else >>emit_jump_insn (gen_return ()); Thanks f

Re: GCC with formal testing docs

2007-07-24 Thread Manuel López-Ibáñez
On 24/07/07, 张飞 <[EMAIL PROTECTED]> wrote: Hi: I know GCC is a wonderful compiler collection. I like it and trust it. But, I can't find any formal docs about Testing GCC, both unit testing and integrat testing. I think, as a software, GCC should be tested and own a test report. http://www.g

bootstrap broken on trunk r126866

2007-07-24 Thread Thomas Veith
Hi *, bootstrap is broken on trunk rev. 126866 during Stage3: libtool: compile: /home/xtv/gcc-devel/gcc/obj/./gcc/xgcc -B/home/xtv/gcc-devel/gcc/obj/./gcc/ -B/home/xtv/i686-pc-linux-gnu/bin/ -B/home/xtv/i686-pc-linux-gnu/lib/ -isystem /home/xtv/i686-pc-linux-gnu/include -isystem /home/xtv/i

BB_RTL flag assertion on basic_block-s when dump_bb_info (and compiler probe)

2007-07-24 Thread Basile STARYNKEVITCH
Hello All, Those interested in my compiler probe (see my talk at GCC Summit 2007) could glance a snapshot on http://starynkevitch.net/Basile/gcc-probe-combine.png and download a patch from http://starynkevitch.net/Basile/basile-ggcc-patches.tgz (which is updated frequently) Now a question abo