-
Notifications
You must be signed in to change notification settings - Fork 69
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
vcruntime: Fix and enable RTTI #391
Merged
Merged
Changes from all commits
Commits
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,3 +33,11 @@ extern "C" | |
return hash; | ||
} | ||
} | ||
|
||
type_info::~type_info() noexcept | ||
{ | ||
} | ||
|
||
type_info::type_info () noexcept | ||
{ | ||
} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,8 +12,8 @@ | |
|
||
struct __std_type_info_data | ||
{ | ||
char const *_UndecoratedName; | ||
char const _DecoratedName[1]; | ||
char *_UndecoratedName; | ||
char _DecoratedName[1]; | ||
}; | ||
|
||
extern "C" | ||
|
@@ -25,7 +25,7 @@ extern "C" | |
class type_info | ||
{ | ||
public: | ||
virtual ~type_info (); | ||
virtual ~type_info () noexcept; | ||
|
||
const char *name () const noexcept | ||
{ | ||
|
@@ -60,7 +60,11 @@ class type_info | |
} | ||
|
||
private: | ||
type_info (type_info const &) = delete; | ||
// According to the standard, this constructor should not exist. However, | ||
// not having any constructors causes LLVM to not emit a vftable. | ||
type_info () noexcept; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please create an issue about this. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. |
||
|
||
type_info (type_info const &) noexcept = delete; | ||
type_info &operator= (type_info const &) = delete; | ||
|
||
mutable __std_type_info_data _Data; | ||
|
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.
If we demangle at runtime, how will we know when to do it?
Wouldn't it have made more sense to keep it
const
and deal with it when implementing demangling?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.
MS demangles the name when
type_info::name()
is called and_UndecoratedName
isNULL
. It allocates a buffer for the string, demangles, and puts the address of the string in_UndecoratedName
.I don't think there's a significant benefit in keeping or removing
const
at this moment - it just bothered me because it was incorrect.