[Bug c/70665] Seemingly incorrect warning for being const correct with function pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70665 --- Comment #2 from Phillipi Susi --- Yes, so why is there an implicit conversion that does not cause a warning when called directly, but not when called via pointer?

[Bug c/70665] New: Seemingly incorrect warning for being const correct with function pointers

: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: psusi at ubuntu dot com Target Milestone: --- void foo( const char *p ); void bar( char *p ) { foo( p ); } This is perfectly acceptable and const correct since foo does not want