Opened 3 years ago

Last modified 9 months ago

#7660 new bug

warning: conflicting types when compiling via-C

Reported by: singpolyma Owned by:
Priority: normal Milestone: 7.12.1
Component: Compiler Version: 7.7
Keywords: warning Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Other Test Case:
Blocked By: Blocking:
Related Tickets: Differential Revisions:

Description

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]

Change History (5)

comment:1 Changed 2 years ago by igloo

  • difficulty set to Unknown
  • Owner set to igloo

Thanks for the report; I'll take a look

comment:2 Changed 2 years ago by igloo

  • Milestone set to 7.8.1

comment:3 Changed 2 years ago by igloo

  • Owner igloo deleted

comment:4 Changed 16 months ago by thoughtpolice

  • Milestone changed from 7.8.3 to 7.10.1

Moving to 7.10.1

comment:5 Changed 9 months ago by thoughtpolice

  • Milestone changed from 7.10.1 to 7.12.1

Moving to 7.12.1 milestone; if you feel this is an error and should be addressed sooner, please move it back to the 7.10.1 milestone.

Note: See TracTickets for help on using tickets.