Guy Harris wrote:
On Jan 3, 2013, at 1:40 PM, Jeff Morriss wrote:
Jeff Morriss wrote:
My (Fedora 10) gcc 4.3.2 was also generating this warning; it would seem that a
fair spread of gcc versions seem to have the problem.
I added a configure check to stop using -Wlogical-op if the compiler is
On Jan 3, 2013, at 1:40 PM, Jeff Morriss wrote:
> Jeff Morriss wrote:
>> My (Fedora 10) gcc 4.3.2 was also generating this warning; it would seem
>> that a fair spread of gcc versions seem to have the problem.
>> I added a configure check to stop using -Wlogical-op if the compiler is
>> genera
Jeff Morriss wrote:
My (Fedora 10) gcc 4.3.2 was also generating this warning; it would seem
that a fair spread of gcc versions seem to have the problem.
I added a configure check to stop using -Wlogical-op if the compiler is
generating this warning in r46916.
Interestingly the Ubuntu buildb
On Sat, Dec 29, 2012 at 10:37:42AM -0500, Evan Huus wrote:
> In the meantime, I'm not really sure what the best workaround is...
What about using memchr() ?
This might be little stupid, but if we avoid warning this way (in cost
of some readability)...
Cheers,
Kuba.
__
My (Fedora 10) gcc 4.3.2 was also generating this warning; it would seem
that a fair spread of gcc versions seem to have the problem.
I added a configure check to stop using -Wlogical-op if the compiler is
generating this warning in r46916.
Evan Huus wrote:
While 'separators' is not immediat
While 'separators' is not immediately constant either,
wtap_file_read_till_separator (the function containing the strchr) is
called in only one place, and that call passes in a string constant to
the 'separators' parameter.
GCC is smart enough to figure that out, so __builtin_constant_p [1]
return
Thus wrote Martin Kaiser (li...@kaiser.cx):
> which seems to evaluate on my system (debian squeeze)
more specifically
martin@skogar:~$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-8'
--with-bugurl=file:///usr/share/doc
Dear all,
I get this warning (error) when I compile svn head
peektagged.c: In function ???wtap_file_read_till_separator???:
peektagged.c:150: error: logical ???&&??? with non-zero constant
will always
evaluate as true
make[2]: *** [libwiretap_la-peektagged.lo] Error 1
The offending line is
