-
Notifications
You must be signed in to change notification settings - Fork 296
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
Fix compiler and linker warnings #1605
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1605 +/- ##
======================================
Coverage 0.06% 0.06%
======================================
Files 78 78
Lines 9792 9792
Branches 2457 2457
======================================
Hits 6 6
Misses 9786 9786
Continue to review full report at Codecov.
|
Ready for review! @luizirber, @camillescott, @standage , or @ctb |
Somewhat related, my terminal is filling up with large number of copies of this warning. It has "always" been there but usually only once, is the duplication related to the multiple template instantiations we do for the read parser?
|
SeqAn is heavily templated as well, so that may also be a factor. There are some warnings I see duplicated several times during compilation, but I haven't kept track of which they were and haven't seen a substantial increase since introducing templating to the read parser. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
08c6c9f
to
4295379
Compare
Ok. For sure the original sin comes from seqan being a bit old, hence the warnings. Downside to all the "visual noise" is that I train myself to ignore it all which means sometimes you miss a new warning :-/ |
Yep, the struggle is real |
4295379
to
51a24d6
Compare
@standage this can be merged right? |
"Yes", given the caveats in our current #khmer@slack discussion. |
Had forgotten about that, let's wait for a decision re: merging into |
I am impressed merging master just worked. 😀 |
From scrolling through the travis output there are less warnings, I think. Merge first, squash more warnings later? |
I did have to resolve a couple conflicts, but honestly there were few
enough changes that I could easily have redone the changes manually.
On Thu, Jul 27, 2017 at 7:56 AM Tim Head ***@***.***> wrote:
I am impressed merging master just worked. 😀
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1605 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAimJxylFzhBWr_YZconPjF2alvWHS7Jks5sSKUzgaJpZM4L0EAg>
.
--
…--
Daniel S. Standage, Ph.D.
Postdoctoral Scholar
Lab for Data Intensive Biology
University of California, Davis
|
Most of the remaining warnings are related to the third-party code. But
there are a couple from khmer/oxli.
This isn't an urgent PR. Let's see if we can squash the rest of the
warnings (from our code) before merging.
On Thu, Jul 27, 2017 at 7:58 AM Tim Head ***@***.***> wrote:
From scrolling through the travis output there are less warnings, I think.
Merge first, squash more warnings later?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1605 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAimJ16jbuRQPvgWDuFuBsx_KrNcxTZNks5sSKWWgaJpZM4L0EAg>
.
--
…--
Daniel S. Standage, Ph.D.
Postdoctoral Scholar
Lab for Data Intensive Biology
University of California, Davis
|
Some trivial fix ups to reduce the number of compiler warnings generated by
khmer
.@luizirber do you know what the
-mmacosx-version-min=10.7
really does? I don't really know more than what you can deduce from the name, which makes me wonder if adding it breaks something (we aren't testing for)?make test
Did it pass the tests?