-
Notifications
You must be signed in to change notification settings - Fork 467
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
clang 37: expression with side effects will be evaluated despite being used as an operand to 'typeid' [-Wpotentially-evaluated-expression] #1523
Comments
Is there a "definition of done" for this Bug? I didn't see this warning so far myself? Maybe you could give some more information of used compiler and environment? |
Environment:
libsass: d18808d Full build output: https://gist.github.com/cvrebert/bd95d26561e14de2cead |
We don't see this on the Travis Mac OSX CI build and I don't have access or connection to any Mac, so someone else needs to step in here to analyze this further ... |
Looks like the Travis build is using an older version of clang (and possibly of OS X?):
|
On Fri, 6 Nov 2015, Marcel Greter wrote:
Is there a "definition of done" for this Bug? I didn't see this warning so far myself? Maybe you could give some more information of used compiler and environment?
this was clang 3.7 as the title says... definition of done: potential issue reported by the warning is resolved.
|
On Fri, 6 Nov 2015, Marcel Greter wrote:
We don't see this on the Travis [Mac OSX CI build] [1] and I don't have access or connection to any Mac, so someone else needs to step in here to analyze this further ...
you need clang at least 3.7 on any platform to see this. It's related to rtti and
is probably mit platform-dependent.
|
Fixed in #1707 |
…espite being used as an operand to 'typeid' This is not a useful warning here but simply extracting `*schema->at(0)` to a variable avoids it. Warning example: https://travis-ci.org/sass/libsass/jobs/471245025 Refs sass#1523
…espite being used as an operand to 'typeid' This is not a useful warning here but simply extracting `*schema->at(0)` to a variable avoids it. Warning example: https://travis-ci.org/sass/libsass/jobs/471245025 Refs sass#1523
…espite being used as an operand to 'typeid' This is not a useful warning here but simply extracting `*schema->at(0)` to a variable avoids it. Warning example: https://travis-ci.org/sass/libsass/jobs/471245025 Refs #1523
May or may be not harmless.
The text was updated successfully, but these errors were encountered: