Re: Excessive calls to iterate_phdr during exception handling

2013-05-30 Thread Ryan Johnson
On 29/05/2013 4:13 AM, Richard Biener wrote: On Wed, May 29, 2013 at 2:47 AM, Ian Lance Taylor wrote: On Mon, May 27, 2013 at 3:20 PM, Ryan Johnson wrote: I have a large C++ app that throws exceptions to unwind anywhere from 5-20 stack frames when an error prevents the request from being serv

gcc-4.8-20130530 is now available

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

Re: gcc4.7.2: try/finally, CLOBBER

2013-05-30 Thread Andrew Pinski
On Thu, May 30, 2013 at 3:31 PM, Ian Lance Taylor wrote: > On Thu, May 30, 2013 at 2:07 AM, Vini Kanvar wrote: >> >> gcc-4.7.2 adds exception handling constructs (try/finally block) for >> pointer and array variables. These variables are CLOBBERed in the >> finally block. > > I'm not sure what yo

Re: gcc4.7.2: try/finally, CLOBBER

2013-05-30 Thread Ian Lance Taylor
On Thu, May 30, 2013 at 2:07 AM, Vini Kanvar wrote: > > gcc-4.7.2 adds exception handling constructs (try/finally block) for > pointer and array variables. These variables are CLOBBERed in the > finally block. I'm not sure what you mean by this. An example might help. > What is the meaning and

Gestión, Coordinación e Integración del Almacén en entornos SAP

2013-05-30 Thread Isis Quintero
Gestión, Coordinación e Integración del Almacén en entorno SAP México D.F. 13 y 14 de JUNIO 2013 Gestión, Coordinación e Integración del Almacén en entornos SAP 14 horas de formación intensiva con un programa diseñado a su medida que le ofrece la formación que profesionales como Ud. demandan. *

Re: Question about vectorization limit

2013-05-30 Thread Dehao Chen
ER=/usr/snp/libexec/gcc/x86_64-unknown-linux-gnu/4.7.4/lto-wrapper > Target: x86_64-unknown-linux-gnu > Configured with: ../gcc-4_7-branch/configure --prefix=/usr/snp --with-gnu-as > --with-gnu-ld --enable-languages=fortran --disable-libmudflap > --disable-multilib --disable-nls --w

Re: Question about vectorization limit

2013-05-30 Thread Toon Moene
--prefix=/usr/snp --with-gnu-as --with-gnu-ld --enable-languages=fortran --disable-libmudflap --disable-multilib --disable-nls --with-arch=native --with-tune=native Thread model: posix gcc version 4.7.4 20130530 (prerelease) (GCC) augmented by this single change: toon@super:~/compilers/g

Re: Please document `contrib/download_prerequisites'

2013-05-30 Thread David Edelsohn
On Thu, May 30, 2013 at 9:41 AM, Michael Witten wrote: > That wiki information should be incorporated into what that wiki page > calls `the official installation docs', and the rest of it should > probably be thrown out as superfluous. I agree that information about GCC is randomly spread betwee

Re: Branch prediction

2013-05-30 Thread Andrew Haley
On 05/30/2013 03:03 PM, Raphael Clifford wrote: > Thank you for this. My question was about something more specific > however. I am interested specifically in branch prediction. For > example one could add __builtin_expect or the compiler can use the > information it finds in its profiling. How

Re: Branch prediction

2013-05-30 Thread Raphael Clifford
Thank you for this. My question was about something more specific however. I am interested specifically in branch prediction. For example one could add __builtin_expect or the compiler can use the information it finds in its profiling. How is this information used by gcc to provide optimised ass

Re: Branch prediction

2013-05-30 Thread Jan Hubicka
> Is there any documentation for what gcc does with branch prediction > information it gets from profiling? I am interested in this for > modern Pentium processors where you can no longer give hints. The profile feedback drives optimizations (i.e. decision what to optimize for speed and what for

Re: Please document `contrib/download_prerequisites'

2013-05-30 Thread Michael Witten
On Thu, 30 May 2013 11:04:55 +0800, Chung-Ju Wu wrote: > 2013/5/30 Michael Witten : >> It would probably be a good idea to mention: >> >> contrib/download_prerequisites >> >> on this page: >> >> http://gcc.gnu.org/install/prerequisites.html >> >> and probably on this page: >> >> http://gcc.g

Re: Excessive calls to iterate_phdr during exception handling

2013-05-30 Thread Torvald Riegel
On Thu, 2013-05-30 at 11:28 +0200, Jakub Jelinek wrote: > On Thu, May 30, 2013 at 11:21:08AM +0200, Torvald Riegel wrote: > > On Tue, 2013-05-28 at 20:30 +0200, Florian Weimer wrote: > > > On 05/28/2013 08:09 PM, Václav Zeman wrote: > > > > > > > If the bottleneck is really in glibc, then you shou

Branch prediction

2013-05-30 Thread Raphael Clifford
Is there any documentation for what gcc does with branch prediction information it gets from profiling? I am interested in this for modern Pentium processors where you can no longer give hints. Specifically I am interested in whether there are in fact any optimisations that work reliably from thi

Re: Excessive calls to iterate_phdr during exception handling

2013-05-30 Thread Jakub Jelinek
On Thu, May 30, 2013 at 11:21:08AM +0200, Torvald Riegel wrote: > On Tue, 2013-05-28 at 20:30 +0200, Florian Weimer wrote: > > On 05/28/2013 08:09 PM, Václav Zeman wrote: > > > > > If the bottleneck is really in glibc, then you should probably ask them > > > to fix it. Could the mutex be changed r

Re: Excessive calls to iterate_phdr during exception handling

2013-05-30 Thread Torvald Riegel
On Tue, 2013-05-28 at 20:30 +0200, Florian Weimer wrote: > On 05/28/2013 08:09 PM, Václav Zeman wrote: > > > If the bottleneck is really in glibc, then you should probably ask them > > to fix it. Could the mutex be changed rwlock instead? > > rwlocks don't eliminate hardware contention, so I doub

Re: Excessive calls to iterate_phdr during exception handling

2013-05-30 Thread Torvald Riegel
On Wed, 2013-05-29 at 10:06 -0400, Ryan Johnson wrote: > On 29/05/2013 9:41 AM, Ian Lance Taylor wrote: > > On Tue, May 28, 2013 at 9:02 PM, Ryan Johnson > > wrote: > >> Maybe I misunderstood... there's currently a (very small) cache > >> (unwind-dw2-fde-dip.c) that lives behind the loader mutex.

gcc4.7.2: try/finally, CLOBBER

2013-05-30 Thread Vini Kanvar
Hi, gcc-4.7.2 adds exception handling constructs (try/finally block) for pointer and array variables. These variables are CLOBBERed in the finally block. What is the meaning and use of CLOBBER? In which cases is it required? What will happen if gcc does not CLOBBER these variables (e.g. gcc-4.6.2