Re: Stack offset computation for incoming arguments.
> Really Appreciate your reply here and made the following changes like
>
> #define ARG_POINTER_REGNUM 8 //Fake hard reg
> #define FRAME _POINTER_REGNUM 9 // Fake hard reg
> #define SP_REG 10
>
> #define ELIMINABLE_REGS { {ARG_POINTER_REGNUM,STACK_POINTER_REGNUM},\
> {ARG_POINTER_REGNUM, FRAME_POINTER_REGNUM}, \
> {FRAME_POINTER_REGNUM, STACK_POINTER_REGNUM} }
I don't understand these changes at all.
> The ARG and FRAME reg are not marked as fixed regs ,but marked as
> call used regs respectively.
If they are fake, you ought to mark them as fixed.
> Please help us regrading with any hints ??
Look at existing ports in the tree with an equivalent setup.
--
Eric Botcazou
gcc-4.7-20140531 is now available
Snapshot gcc-4.7-20140531 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20140531/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_7-branch revision 211106 You'll find: gcc-4.7-20140531.tar.bz2 Complete GCC MD5=daeb75c16b72f2f09be21952f5975509 SHA1=04fac04e3bfb267f3d164f965e973a99c263d6ac Diffs from 4.7-20140524 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.7 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: [GSoC] How to get started with the isl code generation
Hi Tobias, > Allright. It seems you understood the tree traversel. For the actual > patch that we want to commit, let's leave it out for now. Instead, > let's try to get a minimal patch that only adds the flag and the new > file for the isl_ast stuff. In case the isl is choosen as code > generation option, the cloog pass is disabled (they would otherwise get > into their way later) and we dump the ast. We also need a simple test case > that checks that the dump is generated. What do you mean by simple test case that checks that the dump is generated? Is it checking of the dump_flags? > Instead of adding this functionality to gloog() I would create a > semilar function that provides the functionality gloog has for the isl > codegen counterpart. -fgraphite-code-generator switches then between > these two functions. To start with the isl counterpart is almost empty. > It just contains the parts of this patch needed for printing. When we > add more functionality and we encounter reuse opportunities, we can move > parts of graphite-clast-to-gimple.c into a generic codegen file. > > What do you think? I think that it's good. It would help to begin removing of CLooG dependency and make the file with generation of ISL AST easier to maintain. I implemented it in the patch, which can be found below. You can also find my post about my second task of the proposal at the following link http://romangareev.blogspot.com/2014/05/gsoc-report-ii.html -- Cheers, Roman Gareev patch Description: Binary data
question about -ffast-math implementation
I'm trying to copy gcc's behavior with the -ffast-math compiler flag into haskell's ghc compiler. The only documentation I can find about it is at: https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html I understand how floating point operations work and have come up with a reasonable list of optimizations to perform. But I doubt it is exhaustive. My question is: where can I find all the gory details about what gcc will do with this flag? I'm perfectly willing to look at source code if that's what it takes. Also, are there any optimizations that you wish -ffast-math could perform, but for various architectural reasons they don't fit into gcc?
