-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Build error with g++ 9 snapshot #310
Comments
my guess is we just need to cast pointer types explicitly |
I can probably test something. My Docker container with this is still up. |
actually looking at it again i'm confused. seems like maybe we need to be explicit about what template to use? i think you could do something like |
Good call on the cast. A simple I send a PR if it passes Travis. |
nice! |
I'm suddenly getting lots of warnings when compiling with g++ included in Ubuntu 19.10 (which I think is g++ 9). Everything still compiles but all the warnings are a bit frightening :) Is it related to the errors here? |
What we had above were errors which stop us in our tracks. As you mention 19.10, I just installed my RcppAnnoy (wrapper around Annoy) on it, and yes -- with g++-9 I also see warnings but those are just that: warnings. And g++ tells us how to suppress them: add
That said, CRAN is always reminding us that this does get a permanent warning from the SAN/UBSAN analyser ... to which I usually respond that it is "by design". See Edit: Typos edited on 05 Jan 2020. |
Thanks! Adding |
While gcc 9 is of course still unreleased, someone looking after the CRAN archive for R already ran some tests, and RcppAnnoy fails to install. I can replicate that under Docker with Debian's
gcc-snapshot
(currently at 20180908). We seeand that code seems unchanged between what I have in RcppAnnoy and Annoy:
This is of course pretty much at the core of Annoy. Thoughts about how to avoid this while not giving up performance?
The text was updated successfully, but these errors were encountered: