how to test library generation

[Tim Prince]

Thomas Koenig wrote:

>On Sun, Aug 28, 2005 at 07:27:45AM -0700, Tim Prince wrote:
>  
>
>>I haven't yet understood how modifications in the .m4 files are 
>>propagated, and how they should be tested.
>>    
>>
>
>What I do is pretty horrible, but at least it works, and I haven't
>found anything else that works.
>
>I copy the libgfortran directory to another location, then run
>./configure --enable-maintainer-mode in that directory.  This
>fails with an error, but only after the Makefile has been generated.
>
>If I then change the m4 files and type 'make generated/*.c', the
>files are correctly regenerated.  I then only need to copy over
>the m4 and generated files over to the original directory.
>
>  
>
If I run libgfortran/configure --enable-maintainer-mode in the 
libgfortran build directory, make causes the sources to be regenerated 
in the source directory, then .o files are rebuilt.  Even on cygwin.

>>I was concerned about propagating excessive source code unrolling into 
>>the complex variants; is that a problem?
>>    
>>
>
>You mean because of register pressure?
>
>  
>
Yes, on the usual 32-bit targets, register pressure could be enough to 
prevent much gain, and there is already enough going on to fill the 
pipelines on those machines.