Conversation
|
Thanks for your pull request, @Geod24! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub fetch digger
dub run digger -- build "master + dmd#10238" |
|
What's the reason for the revert? |
master failing to build on semaphoreci: https://semaphoreci.com/dlang/dmd-2/branches/master |
|
The PR broke SemaphoreCI. Master is currently red: https://semaphoreci.com/dlang/dmd-2 |
|
You can just use |
Sure but I've made changes since the rebase so my original commit is no longer valid. It's not a big deal, I'm just letting you know that this is causing extra work.
I'm not worried about trends. You have every right to revert the commit, but that doesn't mean we can't try to fix it first either. You don't have a responsibility to fix it of course, I was just asking if it could be easily done. If not then by all means go ahead with the revert (not that you need my permission or anything). |
|
Ping @WalterBright, do you want a chance to come up with a quick fix before the change is reverted? Or should we go ahead with the revert now and fix this later? |
|
Interesting, semaphore is currently passing with my PR, which has been rebased with the "remove optabgen": https://semaphoreci.com/dlang/dmd-2/branches/pull-request-10212/builds/22 |
|
Well I couldn't figure out the cause in the few minutes I spent, so don't hold back on my account. I'm off to bed. |
|
I don't see why removing an usused generator can produce different binaries, but I suspect we hit some threshold producing different code due to something like Line 351 in 08c385c in the optimizer. |
|
Maybe #10240 helps. |
|
Thanks @rainers ! |
Reverts #10221
Let's see what SemaphoreCI says.
(I wish Github opened revert branches in forks...)