Re: data type 'struct loop' in MELT

2010-06-17 Thread Basile Starynkevitch
On Sat, 2010-05-15 at 07:51 +0200, Basile Starynkevitch wrote: > On 05/14/2010 10:27 PM, Michael Raitza wrote: > > > > Up to now I have basic support up and running. The hash map to the loop > > is missing and I have not figured out yet what I need it for, but Basile > > mentioned it to be necessar

strange use of function_invariant_p (Was: Re: Followup for reg_equiv_invariant patch: Fix PR39871)

2010-06-17 Thread Joern Rennecke
Quoting Bernd Schmidt : On 06/15/2010 12:55 PM, Bernd Schmidt wrote: On 06/15/2010 08:00 AM, Joern Rennecke wrote: [constants like (plus (REG:SI SP_REG) (symbol_ref foo))] function_invariant_p will accept them. I guess we can change that and not lose anything. This is what I committed a

gcc-4.5-20100617 is now available

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

Re: GCC porting questions

2010-06-17 Thread Ian Lance Taylor
"Radu Hobincu" writes: > The compiler crashes with "Segmentation fault". > 2. When I try "char c = 'c';", the compiler fails an assert: It's time to break out the debugger and look at the source code and figure out what the compiler is doing. Neither of these problems ring any sort of bell for

Re: GCC porting questions

2010-06-17 Thread Radu Hobincu
Hello again, I managed to get the thing working and I have two last issues to solve. 1. My machine does not have any kind of floating point instructions. When I write in the C source code float f = 0.5f; The compiler crashes with "Segmentation fault". Running a gdb on it, the output becomes Pr

Re: Floating Point Representation in libgcc (is IEEE?)

2010-06-17 Thread Paulo J. Matos
On Tue, Jun 15, 2010 at 2:13 PM, Joern Rennecke wrote: > > It is using whatever floating point format the target has. > If you don't have hardware floating point support, then you get to > choose the format when you design your ABI. Yes, my target has no fp. Thanks! This is not mine to decide if

Re: RFC: ARM Cortex-A8 and floating point performance

2010-06-17 Thread David Brown
On 16/06/2010 17:09, Andrew Pinski wrote: On i?86 we have -mfpmath={sse,x87}, I suppose you could add -mfpmath=neon for arm (properly conflicting with -mfloat-abi=hard and requiring neon support). Except unlike sse, neon does not fully support IEEE support. So this should only be done with

Re: Question about polyhedral model and solver used in GRAPHITE

2010-06-17 Thread Tobias Grosser
On 06/17/2010 10:41 AM, Simone Pellegrini wrote: Dear all, I was reading one of the first technical reports of GRAPHITE and it looks like several libraries have been considered for integration into GCC for solving the ILP problem and polyhedral model representation. In the document the Omega libr

Re: RFC: ARM Cortex-A8 and floating point performance

2010-06-17 Thread Siarhei Siamashka
On Wednesday 16 June 2010 15:22:32 Ramana Radhakrishnan wrote: > On Wed, 2010-06-16 at 15:52 +, Siarhei Siamashka wrote: > > Currently gcc (at least version 4.5.0) does a very poor job generating > > single precision floating point code for ARM Cortex-A8. > > > > The source of this problem is t

Question about polyhedral model and solver used in GRAPHITE

2010-06-17 Thread Simone Pellegrini
Dear all, I was reading one of the first technical reports of GRAPHITE and it looks like several libraries have been considered for integration into GCC for solving the ILP problem and polyhedral model representation. In the document the Omega library, PIP, PolyLib and PPL are mentioned. I am