-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Remove dependency on libgcc-dw2-1.dll from win32 executables. #29177
Merged
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
1da4662
Revisit implementation of custom unwind resume;
vadimcn def917a
Implement `eh_unwind_resume` in libstd.
vadimcn c807ff3
Create entry points for unwind frame registry in libstd.
vadimcn bd0cf1b
Don't use GCC's startup objects (crtbegin.o/crtend.o); build and use …
vadimcn adce670
Fix up tests and docs.
vadimcn 145b843
Use `cfg_attr` for switching `link` attrs in libunwind.
vadimcn 9a71c5c
Use `gcc -print-file-name` for finding C runtime startup objects:
vadimcn d710f8b
Moar comments.
vadimcn afc3046
Drop `advapi32` and `shell32` from late_link_args.
vadimcn 0332ee9
Fix stage0 ICE caused by the old _Unwind_Resume override trickery.
vadimcn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Use
cfg_attr
for switching link
attrs in libunwind.
- Loading branch information
commit 145b8438fe19b81d964b60132eeeb6c95e8646e9
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
So just to clarify
gcc_eh
is a static library which contains all these unwinding functions? We were just previously linking to the dynamic version and using those instead?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.
Er actually... let me rephrase, can you clarify what
gcc_eh
is?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.
Yes,
gcc_eh
exports all those_Unwind_XXX
functions. The dynamic version of libgcc, is actually a bundle oflibgcc.a
andlibgcc_eh.a
.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.
Ah ok, so I know that with MinGW you can sometimes get seh, dwarf, or sjlj exceptions, so does that matter here? For example I think we're basically only compatible with the dwarf strategy on 32-bit and seh on 64 (right?) and is
gcc_eh
just whatever the installation happens to be? Or is it guaranteed to always be the one we use?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.
Yes,
gcc_eh
depends on the flavor of gcc installed. If it's thesjlj
one, we'll just fail to link, I think.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.
Ah and as one final clarification, after talking with @brson, so this means that we are statically linking the unwinding support into the standard library? If so, should this be
kind = "static"
? Also if so, we may want to checkup on the licenses to ensure that we're covered to statically link this code from gcc (we probably are though)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.
It probably should. However this doesn't work right now, because it's in the system libs directory, which rustc is not aware of, so it fails to find it.
Yes, I believe so. libgcc_eh is covered by the linking exception.
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.
This is the same issue that I've been complaining about with getting dllimport fixed.