Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some warning from MinGW under Windows #2790

Closed
escherstair opened this issue Apr 15, 2020 · 8 comments
Closed

Some warning from MinGW under Windows #2790

escherstair opened this issue Apr 15, 2020 · 8 comments
Labels

Comments

@escherstair
Copy link
Contributor

  • libuv v1.35.0
  • Windows 7 SP1 x64
  • MinGW - GCC 7.3.0

Here is the list of some warnings I get from MinW:

for (i = 0; i < ARRAY_SIZE(uv__fd_hash); ++i) {

comparison between signed and unsigned integer expressions [-Wsign-compare]

if (excode != EXCEPTION_IN_PAGE_ERROR) {

comparison between signed and unsigned integer expressions [-Wsign-compare]

int err = 0;

unused variable 'err' [-Wunused-variable]

  • should be included inside #ifdef _MSC_VER / #endif
@stale stale bot added the stale label May 6, 2020
@escherstair
Copy link
Contributor Author

Shuold I provide a PR?

@stale stale bot removed the stale label May 7, 2020
@bnoordhuis
Copy link
Member

@escherstair Yes, please!

@libuv libuv deleted a comment from stale bot May 8, 2020
@escherstair
Copy link
Contributor Author

Give me some time and I'll do it.

@escherstair
Copy link
Contributor Author

I've just added the PR #2854

@escherstair
Copy link
Contributor Author

escherstair commented May 17, 2020

One thing is not clear to me:
variable zero

LARGE_INTEGER zero, pos, end_pos;

is set
zero.QuadPart = 0;

but never used.
If it's not needed I can delete it, otherwise I need to know where it should be used.

@bnoordhuis
Copy link
Member

@escherstair zero can be removed, that was an oversight in 2c27950.

@escherstair
Copy link
Contributor Author

I pushed a commit that removes it

@stale
Copy link

stale bot commented Jun 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 8, 2020
@stale stale bot closed this as completed Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants