#457 Investigate and solve compiler warnings.

Open
opened 2 years ago by wolfbeast · 1 comments
wolfbeast commented 2 years ago (Migrated from github.com)

For as far as our own (not third-party) code is concerned, we should investigate and where possible solve compiler warnings emitted by the build process.

For as far as our own (not third-party) code is concerned, we should investigate and where possible solve compiler warnings emitted by the build process.
trav90 commented 2 years ago (Migrated from github.com)
Owner

Fixes for the remaining -Wclass-memaccess (GCC8) warnings in /js are not trivial and have (so far) only caused build bustage in my attempts to port additional fixes the past few days. I am likely going to have to leave fixing these to someone more knowledgeable with the code in /js.

Also posting a list of current -Wunused-but-set-variable, -Wunused-variable, & -Wunused-function warnings displayed by GCC 7.3 for reference: https://gist.github.com/trav90/19cf4a2de35ac794f382b780074ea2e4

Fixes for the remaining -Wclass-memaccess (GCC8) warnings in /js are not trivial and have (so far) only caused build bustage in my attempts to port additional fixes the past few days. I am likely going to have to leave fixing these to someone more knowledgeable with the code in /js. Also posting a list of current -Wunused-but-set-variable, -Wunused-variable, & -Wunused-function warnings displayed by GCC 7.3 for reference: https://gist.github.com/trav90/19cf4a2de35ac794f382b780074ea2e4
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.