-
Notifications
You must be signed in to change notification settings - Fork 273
C front-end: tolerate type differences with asm renaming #7584
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
base: develop
Are you sure you want to change the base?
C front-end: tolerate type differences with asm renaming #7584
Conversation
The example found in glibc shows how asm renaming may be combined with changes in return type names (even when there isn't actually a bit-level difference amongst the types). Weakening the asm-renamed declaration by marking it "incomplete" works around this problem.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #7584 +/- ##
===========================================
+ Coverage 78.36% 78.50% +0.14%
===========================================
Files 1670 1670
Lines 191768 191770 +2
===========================================
+ Hits 150277 150551 +274
+ Misses 41491 41219 -272
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@@ -646,6 +646,8 @@ void c_typecheck_baset::apply_asm_label( | |||
{ | |||
symbol.name=asm_label; | |||
symbol.base_name=asm_label; | |||
if(symbol.type.id() == ID_code) |
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.
An explaining comment would be great here.
The example found in glibc shows how asm renaming may be combined with changes in return type names (even when there isn't actually a bit-level difference amongst the types). Weakening the asm-renamed declaration by marking it "incomplete" works around this problem.