~drizzle-trunk/drizzle/development

Viewing all changes in revision 1819.9.4.

  • Committer: Stewart Smith
  • Author(s): Davi Arnaut, Stewart Smith
  • Date: 2010-11-17 03:37:51 UTC
  • mto: (2021.1.2 build)
  • mto: This revision was merged to the branch mainline in revision 1971.
  • Revision ID: stewart@flamingspork.com-20101117033751-skszaqrki86evwfq
Merge Revision revid:davi.arnaut@sun.com-20100702183047-fyw33fu1rc9j6qzw from MySQL InnoDB

For drizzle, it's just one fix in Innobase that (obviously) doesn't show up
in our GCC versions (but maybe does elsewhere)

Original revid:davi.arnaut@sun.com-20100702183047-fyw33fu1rc9j6qzw

Original Authors: Davi Arnaut <Davi.Arnaut@Sun.COM>
Original commit message:
Bug#53445: Build with -Wall and fix warnings that it generates

Apart strict-aliasing warnings, fix the remaining warnings
generated by GCC 4.4.4 -Wall and -Wextra flags.

One major source of warnings was the in-house function my_bcmp
which (unconventionally) took pointers to unsigned characters
as the byte sequences to be compared. Since my_bcmp and bcmp
are deprecated functions whose only difference with memcmp is
the return value, every use of the function is replaced with
memcmp as the special return value wasn't actually being used
by any caller.

There were also various other warnings, mostly due to type
mismatches, missing return values, missing prototypes, dead
code (unreachable) and ignored return values.

expand all expand all

Show diffs side-by-side

added added

removed removed

Lines of Context: