Skip to content

OpenSSL windows asm question #7426

Description

@indutny

Part 1

01fa5ee

What is the purpose of this? cc @piscisaureus

As far as I get it - GYP option may be used to enable this: https://github.com/svn2github/gyp/blob/e0ee72ddc7fb97eb33d530cf684efcbe4d27ecb3/test/win/ml-safeseh/ml-safeseh.gyp#L18-L20

Part 2

What is the purpose of /Zi? I know that it generates debug info, but can't see why it is needed. cc @piscisaureus again

cc @nodejs/collaborators just in case.

Reasoning

I'm thinking about removing rules from the gyp.js as I don't really like the feature bloat that it has. It looks like Node builds just fine without these rules

Activity

  1. indutny commented on Jun 26, 2016

    @indutny
    MemberAuthor

    For part 2 DebugInformationFormat option may be used as well.

  2. indutny commented on Jun 26, 2016

    @indutny
    MemberAuthor

    Also, .asm files are supported by GYP since I don't know what time, so there is no reason to have extra rules for them.

  3. added
    windowsIssues and PRs related to the Windows platform.
    opensslIssues and PRs related to the OpenSSL dependency.
    on Jun 26, 2016
  4. added a commit that references this issue on Jun 26, 2016
    eb57503
  5. indutny commented on Jun 26, 2016

    @indutny
    MemberAuthor

    Proposed change: #7427

  6. bnoordhuis commented on Jun 26, 2016

    @bnoordhuis
    Member

    01fa5ee

    Not a Windows compiler/linker expert but I suspect that without /safeseh you wouldn't be able to link add-ons that depend on SafeSEH.

  7. eljefedelrodeodeljefe commented on Jun 26, 2016

    @eljefedelrodeodeljefe
    Contributor

    +1 for removing /Zi, also for all that .pdb files and manifests and some assembly inlining. For some of those flags even the MSDN pages warn for extreme file bloat.

    /SafeSEH: I can only guess, but I assume it predates the current compilation workflow, where openssl has been compiled with an older compiler, that didn't include /safeseh and we wanted to protect against it. The MSDN page contradicts the commit message, as the flag does not mark afile, but protect against it at compile time. I found this to be useful, when I decided to exclude it. However it should not be expensive to let it in.

  8. piscisaureus commented on Jun 27, 2016

    @piscisaureus
    Contributor

    @indutny, @eljefedelrodeodeljefe: for /safeseh: see nodejs/node-v0.x-archive#4242

    I think you can drop /Zi.

  9. indutny commented on Jun 27, 2016

    @indutny
    MemberAuthor

    @piscisaureus thank you, asked you a question in #7427 ;)

  10. added a commit that references this issue on Sep 3, 2016
    72a08e2
  11. added a commit that references this issue on Sep 4, 2016
    ef977f6
  12. added a commit that references this issue on Sep 28, 2016
    77827eb
  13. added a commit that references this issue on Oct 18, 2016
    0e1162c
  14. added a commit that references this issue on Oct 26, 2016
    ea36c61
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

    opensslIssues and PRs related to the OpenSSL 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