Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 30 Jun 2015, 10:55
All times are UTC - 4
 Forum index » Off-Topic Area » Programming
Some cflags questions...
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 1 of 1 Posts_count_1  
Author Message

Joined: 13 Sep 2009
Posts: 168
Location: The middle of a cornfield

PostPosted: Sat 07 Nov 2009, 21:23    Post_subject:  Some cflags questions...  

This is a snippet from a chromium build configuration file

  'conditions': [
    [ 'OS=="linux"', {
      'target_defaults': {
        'asflags': [
          # Needed so that libs with .s files (e.g. libicudata.a)
          # are compatible with the general 32-bit-ness.
        # All floating-point computations on x87 happens in 80-bit
        # precision.  Because the C and C++ language standards allow
        # the compiler to keep the floating-point values in higher
        # precision than what's specified in the source and doing so
        # is more efficient than constantly rounding up to 64-bit or
        # 32-bit precision as specified in the source, the compiler,
        # especially in the optimized mode, tries very hard to keep
        # values in x87 floating-point stack (in 80-bit precision)
        # as long as possible. This has important side effects, that
        # the real value used in computation may change depending on
        # how the compiler did the optimization - that is, the value
        # kept in 80-bit is different than the value rounded down to
        # 64-bit or 32-bit. There are possible compiler options to make
        # this behavior consistent (e.g. -ffloat-store would keep all
        # floating-values in the memory, thus force them to be rounded
        # to its original precision) but they have significant runtime
        # performance penalty.
        # -mfpmath=sse -msse2 makes the compiler use SSE instructions
        # which keep floating-point values in SSE registers in its
        # native precision (32-bit for single precision, and 64-bit for
        # double precision values). This means the floating-point value
        # used during computation does not change depending on how the
        # compiler optimized the code, since the value is always kept
        # in its specified precision.
        'cflags': [

SSE2 instructions are not supported on AMD athalon, pentium 3, or AMD k6 processors. (and probably more) I know I'm going to have to take out the '-msse2' line but what about the other lines?
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 1 of 1 Posts_count_1  
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Off-Topic Area » Programming
Jump to:  

You cannot attach files in this forum
You can download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0401s ][ Queries: 11 (0.0027s) ][ GZIP on ]