On Tue, Nov 15, 2005 at 06:38:33AM +0100, Vincent Torri wrote:
> 
> maybe one should test in configure.in if the processor is an mad64 or not,
> then define a specific flag according tot the arch and add it to the flags
> when one compiles.

gcc bugs change greatly between releases ... trying to track which CFLAGS
are 'safe' and which ones are not is a huge pita

a lot easier to say to the user:
dont use stupid optimizations
-mike


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to