Skip to content

warning: conflicting types when compiling via-C

I don't think this is actually a problem per-se, but usually these warnings are indicative of unsafe assumptions being made:

when making flags consistent: Warning:
    Compiler unregisterised, so compiling via C

/tmp/ghc7162_0/ghc7162_0.hc:1164:1:
     warning: conflicting types for built-in function 'memchr' [enabled by default]

/tmp/ghc7162_0/ghc7162_0.hc:6885:1:
     warning: conflicting types for built-in function 'memset' [enabled by default]

/tmp/ghc7162_0/ghc7162_0.hc:8594:1:
     warning: conflicting types for built-in function 'memcpy' [enabled by default]

/tmp/ghc7162_0/ghc7162_0.hc:11521:1:
     warning: conflicting types for built-in function 'free' [enabled by default]

/tmp/ghc7162_0/ghc7162_0.hc:11522:1:
     warning: conflicting types for built-in function 'realloc' [enabled by default]

/tmp/ghc7162_0/ghc7162_0.hc:12038:1:
     warning: conflicting types for built-in function 'malloc' [enabled by default]

/tmp/ghc7162_0/ghc7162_0.hc:13583:1:
     warning: conflicting types for built-in function 'strlen' [enabled by default]

/tmp/ghc7162_0/ghc7162_0.hc:13994:1:
     warning: conflicting types for built-in function 'memcmp' [enabled by default]
Trac metadata
Trac field Value
Version 7.7
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information