gcc-4.6-20110527 is now available

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

Re: how to distinguish patched GCCs

2011-05-27 Thread Nathan Froyd
On Fri, May 27, 2011 at 06:30:21AM -0700, Ian Lance Taylor wrote: > Jonathan Wakely writes: > > It's an additional maintenance burden. > > It's not a maintenance burden on gcc, though. > > I think we should have the gcc configure script provide a way to add a > preprocessor macro. FWIW, we decide

Re: how to distinguish patched GCCs

2011-05-27 Thread Toon Moene
On 05/27/2011 11:33 AM, Matthias Kretz wrote: True. Right now I'm forced to do this. But I know my users... have you seen the typical physicist developing HPC software? ;) Sure - I am one. I know what you refer to. That's why *I* install versions of gcc/gfortran for them. [ Famous quote o

Re: Several "warning: cannot export hidden symbol" during x86_64-apple-darwin10 bootstrap

2011-05-27 Thread Jack Howarth
On Fri, May 27, 2011 at 11:30:44AM +0200, Paolo Carlini wrote: > Hi, > > > Should I open a PR for them? > > What do they mean? It means that a linker script pattern matches something > which can't be actually exported? This error message may be coming from the following code... http://www.open

Re: how to distinguish patched GCCs

2011-05-27 Thread Ian Lance Taylor
Jonathan Wakely writes: > It's an additional maintenance burden. It's not a maintenance burden on gcc, though. I think we should have the gcc configure script provide a way to add a preprocessor macro. That would not be hard for somebody to implement (perhaps Matthias), it should not pose a si

Re: finding the induction variable after graphite (before ivcanon pass)?

2011-05-27 Thread Alexey Kravets
Hi Sebastian, On 05/26/2011 07:20 PM, Sebastian Pop wrote: I see. Would it be possible to strip mine the reduction loop that you say not handled yet, and then translate to opencl the partial sums? We believe it would be quite difficult. This problem can be divided into three sub-problems: 1.

Re: how to distinguish patched GCCs

2011-05-27 Thread Jakub Jelinek
On Fri, May 27, 2011 at 11:46:27AM +0200, Richard Guenther wrote: > At SUSE we didn't yet see a need for this kind of macro. Not sure > what RedHat uses it for. To make use of new features backported to older compilers. E.g. our has: /* GCC 4.3 and above allow passing all anonymous arguments of

Re: how to distinguish patched GCCs

2011-05-27 Thread Richard Guenther
On Fri, May 27, 2011 at 11:33 AM, Matthias Kretz wrote: > On Friday 27 May 2011 11:14:38 Richard Guenther wrote: >> I know developing on the edge of what compilers support can be a PITA, >> but it's more maintainable to have checks and workarounds in terms >> of actual bugs than compiler versions.

Re: how to distinguish patched GCCs

2011-05-27 Thread Matthias Kretz
On Friday 27 May 2011 11:14:38 Richard Guenther wrote: > I know developing on the edge of what compilers support can be a PITA, > but it's more maintainable to have checks and workarounds in terms > of actual bugs than compiler versions. Full ack. > It should be relatively easy for > you to provi

Re: Several "warning: cannot export hidden symbol" during x86_64-apple-darwin10 bootstrap

2011-05-27 Thread Paolo Carlini
Hi, > Should I open a PR for them? What do they mean? It means that a linker script pattern matches something which can't be actually exported? > Paolo

Re: how to distinguish patched GCCs

2011-05-27 Thread Matthias Kretz
On Friday 27 May 2011 11:02:14 Jonathan Wakely wrote: > It's an additional maintenance burden. For packagers? They have all required version information in their own packaging setups already. All they need to implement is a way to automatically convert that into a configure switch. Once this is

Several "warning: cannot export hidden symbol" during x86_64-apple-darwin10 bootstrap

2011-05-27 Thread Dominique Dhumieres
Paolo, While chasing bootstrap failures on Darwin, I did notice the following (harmless) warnings: ld: warning: cannot export hidden symbol std::basic_stringbuf, std::allocator >::~basic_stringbuf() from .libs/complex_io.o ld: warning: cannot export hidden symbol std::basic_stringbuf, std::alloc

Re: how to distinguish patched GCCs

2011-05-27 Thread Richard Guenther
On Fri, May 27, 2011 at 11:02 AM, Jonathan Wakely wrote: > On 27 May 2011 09:46, Matthias Kretz wrote: >>> >>> The cases where you have to work around compiler issues in a >>> _header_ file should be very rare. >> >> And? Because they are rare we shouldn't care? I'm developing a template >> librar

Re: how to distinguish patched GCCs

2011-05-27 Thread Jonathan Wakely
On 27 May 2011 09:46, Matthias Kretz wrote: >> >> The cases where you have to work around compiler issues in a >> _header_ file should be very rare. > > And? Because they are rare we shouldn't care? I'm developing a template > library for SSE, AVX, LRBni, ... and this stuff is like daily bread for

Re: how to distinguish patched GCCs

2011-05-27 Thread Matthias Kretz
On Thursday 26 May 2011 12:18:19 Richard Guenther wrote: > On Thu, May 26, 2011 at 12:06 PM, Matthias Kretz wrote: > > __GNUC_DISTRIBUTOR___ > > This macro is defined in releases of GCC that are prepared by entities > > other than the FSF. The actual name of the macro depends on the value > > set