镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

NodeJs v8.0.0-v8.1.0, C4716: 'v8::ArrayBuffer::Allocator::Reserve': must return a value #13392

Description

@prepare

Do you forget to return the value ?

C4716: 'v8::ArrayBuffer::Allocator::Reserve': must return a value

nodejs
version v8.0.0
build from source (TODAY) from main web page (https://nodejs.org/en/download/current/)
platform: build with VS2015, x64, Win7


In main source from webpage.
This file, dep/v8/src/api.cc

node_1

this method (1) should return 'something' (2), it is not void.
so VS2015-> compile error -> semantic check error.


I compare the source from the original main web (3) (https://github.com/nodejs/node/blob/master/deps/v8/src/api.cc#L440)
and the source on github. It has a little diff.


Activity

  1. addaleax commented on Jun 2, 2017

    @addaleax
    Member

    UNIMPLEMENTED() just crashes, there’s no point in returning anything; can you show the actual error that you get from compiling?

  2. added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    v8 engineIssues and PRs related to the V8 dependency.
    windowsIssues and PRs related to the Windows platform.
    on Jun 2, 2017
  3. prepare commented on Jun 2, 2017

    @prepare
    Author

    node_2

    This is the only one error when I build it.

  4. prepare commented on Jun 2, 2017

    @prepare
    Author

    node_3

    To pass that, I fix it by adding return nullptr;

  5. joaocgreis commented on Jun 6, 2017

    @joaocgreis
    Member

    I confirm this happens in debug builds.

  6. prepare commented on Jun 9, 2017

    @prepare
    Author

    Still not fixed in NodeJS v 8.1.0 (main source from webpage)
    err01

  7. aqrln commented on Jun 9, 2017

    @aqrln
    Contributor

    As far as I understand, this is an issue with V8 sources, and thus should be reported in their issue tracker, shouldn't it?

  8. prepare commented on Jun 9, 2017

    @prepare
    Author

    @aqrln,

    But the error is 'included' in nodejs's official source snapshot from nodejs's main page.

    I think we should patch it before release to other node users (that build from src).

    for me, I'm not hurry :)

    But I've never see this (err) before in the official node source.

    :)

  9. gibfahn commented on Jun 9, 2017

    @gibfahn
    Member

    But the error is 'included' in nodejs's official source snapshot from nodejs's main page.

    We take everything in deps/ from the maintainers of those projects, and we try not to float patches unless necessary. So in this case nodejs/node deps/v8/src/api.cc#L436 corresponds to v8/v8 src/api.cc#L452.

    So assuming that this is a V8 issue (and that it's not something special we're doing in Node) the way to get it fixed is to raise it upstream.

  10. addaleax commented on Jun 9, 2017

    @addaleax
    Member

    As far as I understand, this is an issue with V8 sources, and thus should be reported in their issue tracker, shouldn't it?

    Just so you know, this is a temporary situation; these methods will become pure virtual at some point in the (possibly near) future.

    Anyway, here’s an upstream patch: https://codereview.chromium.org/2929993003/

  11. bzoz commented on Jun 9, 2017

    @bzoz
    Contributor

    It happens only in Debug builds because in Release it is suppressed by whole program optimization. When building V8 by itself function level linking is enabled and it also suppress this.

  12. TimothyGu commented on Jun 12, 2017

    @TimothyGu
    Member

    Adding the exact error message so the issue is searchable: C4716: 'v8::ArrayBuffer::Allocator::Reserve': must return a value

  13. 7 remaining items

  14. bzoz commented on Jun 13, 2017

    @bzoz
    Contributor

    Fixed in a0f8faa

  15. added a commit that references this issue on Jun 29, 2017
  16. added a commit that references this issue on Jul 11, 2017
  17. added a commit that references this issue on Jul 18, 2017
  18. added a commit that references this issue on Jul 21, 2017
  19. added a commit that references this issue on Jul 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.v8 engineIssues and PRs related to the V8 dependency.windowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions