RE: Defining a common plugin machinery

2008-10-08 Thread Grigori Fursin
> > Personally I'm against the env var idea as it would make it harder to > > figure out what's going on. I think someone mentioned that the same > > effect could be achieved using spec files. > > > Ian mentioned the idea of creating small wrapper scripts with the names: > gcc/g++ etc which just ca

RE: Defining a common plugin machinery

2008-10-08 Thread Grigori Fursin
Ok. I am fine with that. Actually, it requires minor modifications to the GCC anyway, so I can just keep them as patches for the ICI/MILEPOST GCC ;) ... Cheers, Grigori > -Original Message- > From: Taras Glek [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 09, 2008 8:29 AM > To: Gri

Re: Defining a common plugin machinery

2008-10-08 Thread Brendon Costa
> Personally I'm against the env var idea as it would make it harder to > figure out what's going on. I think someone mentioned that the same > effect could be achieved using spec files. > Ian mentioned the idea of creating small wrapper scripts with the names: gcc/g++ etc which just call the re

Re: Defining a common plugin machinery

2008-10-08 Thread Taras Glek
Grigori Fursin wrote: Thanks, Taras! I slightly updated this page, i.e. we would like to be able to load plugins through environment variables to be able to optimize programs transparently as it is done in MILEPOST GCC (without Makefile modifications). By the way, we plan to extend the Interacti

RE: Defining a common plugin machinery

2008-10-08 Thread Grigori Fursin
Thanks, Taras! I slightly updated this page, i.e. we would like to be able to load plugins through environment variables to be able to optimize programs transparently as it is done in MILEPOST GCC (without Makefile modifications). By the way, we plan to extend the Interactive Compilation Interf

Re: register class constraints question

2008-10-08 Thread DJ Delorie
Joern Rennecke <[EMAIL PROTECTED]> writes: > I'm not sure if this changed with IRA, Acts the same with 4.3 and 4.4. > reload will look for the alternative with the cheapest total cost of > alternative and reloads. This was the key. Disparaging the smaller class's alternative with '?' works -

Re: Help with IA64 profiling bug - g++.dg/tree-prof/indir-call-prof.C

2008-10-08 Thread Steve Ellcey
On Thu, 2008-10-09 at 00:27 +0200, Andreas Schwab wrote: > I don't see that problem here. The variable is set at the right places, > except that it is set to the address of the vtable descriptor, which is > different to the normal descriptor. When I modify > __gcov_indirect_call_profiler to com

gcc-4.2-20081008 is now available

2008-10-08 Thread gccadmin
Snapshot gcc-4.2-20081008 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20081008/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.2 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: Help with IA64 profiling bug - g++.dg/tree-prof/indir-call-prof.C

2008-10-08 Thread Andreas Schwab
Steve Ellcey <[EMAIL PROTECTED]> writes: > There seems to be more then just a missing level of dereferencing going > on. For example, I think that the program, when compiled with > -fprofile-generate, should be putting an address into > __gcov_indirect_call_callee before calling __gcov_indirect_c

Re: Help with IA64 profiling bug - g++.dg/tree-prof/indir-call-prof.C

2008-10-08 Thread Steve Ellcey
On Tue, 2008-10-07 at 17:55 +0200, Andreas Schwab wrote: > > I think to make that work tree_gen_ic_profiler and > tree_gen_ic_func_profiler would have to dereference the function > descriptor to extract the code address, which would then have the > necessary uniqueness which the vtable function d

Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-08 Thread Thorsten Glaser
Thomas Schwinge dixit: >First, the check for gcc_cv_libc_provides_ssp is not complete, as has >already pointed out (with patches!) before, but is still not fixed on >trunk. Let me revisit that: in configure.ac it is being checked for >``case "$target" in *-*-linux*)'' which should rather match ``

Re: register class constraints question

2008-10-08 Thread Joern Rennecke
I'm not sure if this changed with IRA, but at least with the old reload code, if the instruction doesn't match, reload will look for the alternative with the cheapest total cost of alternative and reloads. Unfortunately, the fact that some reloads might be impossible does not figure in the decisio

build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR

2008-10-08 Thread Thomas Schwinge
Hello! First, the check for gcc_cv_libc_provides_ssp is not complete, as has already pointed out (with patches!) before, but is still not fixed on trunk. Let me revisit that: in configure.ac it is being checked for ``case "$target" in *-*-linux*)'' which should rather match ``*-*-linux* | *-*-*-g