Skip to content
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

Fix7327 #635

Closed
wants to merge 9 commits into from
Closed

Fix7327 #635

wants to merge 9 commits into from

Conversation

MartinNowak
Copy link
Member

braddr and others added 9 commits March 3, 2012 23:45
when usNumops == 0 and emitting a vector instruction, popndTmp is left uninitialized and is later dereferenced.
…:scan

In Lexer::peek, the code truncated the next list in the case where peek was reentrant.  ie:

  ... peek ... ... peek ...

In TOKpound processing, it should peek relative to the passed in token rather than the global current token.
initialize popndTmp rather than rely on carefulness
fix latent bug with Lexer::peek and recently introduced bug in Lexer::scan
Issue 7038 - Type mismatch with const struct
 - resolve aliases in overload sets
   and nested overload sets
@@ -323,8 +323,10 @@ struct OverloadSet : Dsymbol

OverloadSet();
void push(Dsymbol *s);
virtual int isOverloadable();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bool?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DMD "coding convention" - isOverloadable already exist in Dsymbol..

@andralex
Copy link
Member

I wonder to what extent this moves forward toward overloading as described in TDPL. That is long overdue...

braddr pushed a commit to braddr/dmd that referenced this pull request Oct 22, 2012
Update putAArray for non-x86 architechtures.
@andralex
Copy link
Member

ping - please rebase and let's take this home

@andralex
Copy link
Member

reping

@MartinNowak
Copy link
Member Author

I'll have to rewrite this. We're now doing another overload resolution to check for @property and the code has changed quite a bit in the meantime.
So I wont get to this very soon.

@MartinNowak
Copy link
Member Author

But the fix is pretty simple, we only need to add OverloadSet::isOverloadable and OverloadSet::apply and use apply instead of loops.

@andralex
Copy link
Member

@dawgfoto okay to close this for now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants