[Bug c++/44924] Broken htons, invalid conversion warning

2010-07-24 Thread ralgith at gmail dot com
--- Comment #6 from ralgith at gmail dot com 2010-07-24 20:02 --- Apparently this is fixed in later versions of glibc already. Thanks for the info. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44924

[Bug c++/44924] New: Broken htons, invalid conversion warning

2010-07-12 Thread ralgith at gmail dot com
nu) compiled by GNU C version 4.4.1, GMP version 4.3.1, MPFR version 2.4.1. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: d87da6367e390a0648b100f32b6ee212 cc1plus: warnings being treated as errors imc.c: In function ‘bool imc_startup_por

[Bug c++/44924] Broken htons, invalid conversion warning

2010-07-12 Thread ralgith at gmail dot com
--- Comment #1 from ralgith at gmail dot com 2010-07-12 20:04 --- Created an attachment (id=21187) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21187&action=view) Preprocessor output (.ii) file. This is the output from using --save-temps flag to g++ when trying to comp

[Bug c++/44924] Broken htons, invalid conversion warning

2010-07-12 Thread ralgith at gmail dot com
--- Comment #2 from ralgith at gmail dot com 2010-07-12 20:07 --- This was originally reported and ignored here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39623 Since this ONLY happens with optimization, I'm curious why someone would think it has multiple defines in the arpa he

[Bug c++/44924] Broken htons, invalid conversion warning

2010-07-12 Thread ralgith at gmail dot com
--- Comment #4 from ralgith at gmail dot com 2010-07-12 20:17 --- (In reply to comment #3) > >-Wconversion > Will cause this warning. > > >sa.sin_port = (__extension__ ({ register unsigned short int __v, __x = > (siteinfo->port); if (__builtin_constant_p (_

[Bug c++/33858] Spurious warning with anonymous namespace

2007-10-30 Thread ralgith at gmail dot com
--- Comment #1 from ralgith at gmail dot com 2007-10-30 18:23 --- Or be considered non-local, but NOT generate the warning. This is a fairly common coding convention, and this warning keeps jumping up and down at me in several programs I've compiled. -- ralgith at gmail do