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

fix Issue 23618 - Right Shift equals expressions on unsigned shorts s… #14814

Merged
merged 1 commit into from
Jan 14, 2023

Conversation

WalterBright
Copy link
Member

…hould be unsigned right shift

@dlang-bot
Copy link
Contributor

dlang-bot commented Jan 14, 2023

Thanks for your pull request, @WalterBright!

Bugzilla references

Auto-close Bugzilla Severity Description
23618 blocker Right Shift equals expressions on unsigned shorts should be unsigned right shift

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "stable + dmd#14814"

Copy link
Member

@ibuclaw ibuclaw left a comment

Choose a reason for hiding this comment

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

Don't merge this on master, this is affecting industry.

@ibuclaw ibuclaw added the Review:Industry Applies to PRs pertaining to industry applications of D label Jan 14, 2023
@WalterBright
Copy link
Member Author

@ibuclaw ???

@WalterBright WalterBright added the Review:Blocking Other Work review and pulling should be a priority label Jan 14, 2023
@WalterBright
Copy link
Member Author

I don't understand what change you are requesting. This is listed as a blocker bug. The fix is isolated to dmd. You said that gdc and ldc don't have this issue.

@dkorpel
Copy link
Contributor

dkorpel commented Jan 14, 2023

The requested change is to target stable

@WalterBright
Copy link
Member Author

  1. this problem has been there for many years, with apparently nobody reporting it. I don't see a rush to put it into stable
  2. it carries a small risk of someone relying on the old behavior. That should disqualify it from stable.

@WalterBright
Copy link
Member Author

But you can put it in stable if you prefer. I just want it fixed.

@dkorpel dkorpel changed the base branch from master to stable January 14, 2023 10:30
@dkorpel dkorpel dismissed ibuclaw’s stale review January 14, 2023 10:30

Not targeting master anymore

@dkorpel dkorpel merged commit 579c97a into dlang:stable Jan 14, 2023
@ibuclaw
Copy link
Member

ibuclaw commented Jan 14, 2023

But you can put it in stable if you prefer. I just want it fixed.

Putting things in master won't fix the problem, you're just delaying the fix being released until 3 months down the line. In the meantime companies are complaining and want it released now.

@WalterBright WalterBright deleted the fix23618 branch January 14, 2023 18:47
@WalterBright
Copy link
Member Author

Thanks all for taking care of this.

@CyberShadow
Copy link
Member

"Companies want [breaking change] right now" is perhaps not a good scalable approach in general.

Not that there isn't the problem that different users of D will want different proportions of stability vs. hotfixes (which suit them in that moment). I know Digger isn't amazing right now but I think having tooling which allows building site-specific variants of D is the best general solution to these problems.

@ibuclaw
Copy link
Member

ibuclaw commented Jan 15, 2023

"Companies want [breaking change] right now" is perhaps not a good scalable approach in general.

Both GDC and LDC produce the correct code, as well as any C/C++ compiler (apart from DMC it seems, if I understand the version(MARS) condition right). DMD is just plain wrong here.

dkorpel pushed a commit to WalterBright/dmd that referenced this pull request Jan 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Merge:auto-merge Review:Blocking Other Work review and pulling should be a priority Review:Industry Applies to PRs pertaining to industry applications of D Severity:Bug Fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants