This comment has been minimized.

@WalterBright I just successfully built and tested the entire DMD toolchain on OS X (both in 32-bit and 64-bit mode). I really can't seem to reproduce these issues... Can you give me specific instructions on how to repro?

@WalterBright I just successfully built and tested the entire DMD toolchain on OS X (both in 32-bit and 64-bit mode). I really can't seem to reproduce these issues... Can you give me specific instructions on how to repro?

This comment has been minimized.

I tried repulling the files. Same problem. That's why I asked you to email which files you are using. I will test them, if they work, I will push them to github. If not, I will revert to the ones that do work.

I tried repulling the files. Same problem. That's why I asked you to email which files you are using. I will test them, if they work, I will push them to github. If not, I will revert to the ones that do work.

This comment has been minimized.

I tried repulling the files. Same problem. That's why I asked you to email which files you are using. I will test them, if they work, I will push them to github. If not, I will revert to the ones that do work.

I understand. I'll wait your commit or reverting.

Sorry for my work that have complicated the situation. I got a bitter experience:
”If there is a broken head, reverting commits that breaks it is the only way we can do."
That is my mistake.

I tried repulling the files. Same problem. That's why I asked you to email which files you are using. I will test them, if they work, I will push them to github. If not, I will revert to the ones that do work.

I understand. I'll wait your commit or reverting.

Sorry for my work that have complicated the situation. I got a bitter experience:
”If there is a broken head, reverting commits that breaks it is the only way we can do."
That is my mistake.

This comment has been minimized.

@klickverbot:
Current lastest master has a problem with debug build. It's reported by @jmdavis in newsgroup, and @alexrp has been posted the pull #1051 to fix the problem.
I have already verified that the #1051 fixes the reported ICE problem in my Windows PC, but, it's yet not confirmed whether the undefined symbols problems reported by Walter is really fixed with #1051.
If #1051 will fix his problem, it will be merged. Otherwise all of changes will be reverted.

@klickverbot:
Current lastest master has a problem with debug build. It's reported by @jmdavis in newsgroup, and @alexrp has been posted the pull #1051 to fix the problem.
I have already verified that the #1051 fixes the reported ICE problem in my Windows PC, but, it's yet not confirmed whether the undefined symbols problems reported by Walter is really fixed with #1051.
If #1051 will fix his problem, it will be merged. Otherwise all of changes will be reverted.

This comment has been minimized.

@9rnsr: Sorry, master was not entirely accurate, I already applied #1051. I sincerely hope the changes won't just reverted, as it doesn't seem likely that e.g. _D3std5array17T8AppenderTAyaZ8Appender11newCapacityFkZk being reported as missing is a consequence of this pull request. Rather, it seems like Walter's build environment is broken (stale files, …).

@9rnsr: Sorry, master was not entirely accurate, I already applied #1051. I sincerely hope the changes won't just reverted, as it doesn't seem likely that e.g. _D3std5array17T8AppenderTAyaZ8Appender11newCapacityFkZk being reported as missing is a consequence of this pull request. Rather, it seems like Walter's build environment is broken (stale files, …).

This comment has been minimized.

Rather, it seems like Walter's build environment is broken (stale files, …).
Maybe. But, there may be other real problems.

I've learned a serious experience by this matter: if merging a pull request causes the auto-tester breaking, we should revert it as far as possible, rather than adding more fixture commits. And it is that Walter was always doing.

Rather, it seems like Walter's build environment is broken (stale files, …).
Maybe. But, there may be other real problems.

I've learned a serious experience by this matter: if merging a pull request causes the auto-tester breaking, we should revert it as far as possible, rather than adding more fixture commits. And it is that Walter was always doing.

This comment has been minimized.

I've emailed the files, but I can guarantee you that they are bit-exactly equal to the files currently in Git HEAD. If, when you copy the files over locally, you have differences, something must have gone wrong when you pulled from GitHub...

Maybe you could describe your typical workflow in synchronizing with new changes on GitHub?

I've emailed the files, but I can guarantee you that they are bit-exactly equal to the files currently in Git HEAD. If, when you copy the files over locally, you have differences, something must have gone wrong when you pulled from GitHub...

Maybe you could describe your typical workflow in synchronizing with new changes on GitHub?