VoidPadding: Let [VOID] Handle Padding in Masked Diffusion Language Models so that [EOS] Can Focus on Semantic Termination
The paper proposes VoidPadding, a method that decouples padding and termination roles in Masked Diffusion Language Models by introducing a dedicated [VOID] token for padding, which resolves [EOS] overflow issues and significantly improves performance and decoding efficiency on instruction-tuned models.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are teaching a robot to write stories. In the old way (Autoregressive models), the robot writes one word at a time, left to right, like a human typing. But in this new method called Masked Diffusion, the robot starts with a blank page full of question marks and tries to guess all the words at once, refining its guesses over and over until the story makes sense.
The problem the paper identifies is that when we teach this robot, we have to give it practice examples. To make the practice efficient, we take short stories and pad them with "dummy words" so they all fit on the same size page.
The Problem: The Confused "Stop" Sign
In the past, researchers used a special token called [EOS] (End of Sentence) as that "dummy word."
- Its Job 1: To tell the robot, "Stop writing here, the story is done."
- Its Job 2: To fill up empty space on the page so the robot can practice.
The paper argues that giving the [EOS] token these two jobs is like asking a traffic light to be both a Stop sign and a construction barrier.
When the robot is practicing, it learns that [EOS] means "fill this space." But when it's actually writing a real story, it sees [EOS] and gets confused. It thinks, "Oh, I need to fill this space with more [EOS]s!" This causes a glitch called [EOS] overflow. The robot writes a tiny bit of text and then just spam-fills the rest of the page with "End of Sentence" markers, cutting the story short.
This gets worse when the robot tries to write long stories in big chunks (large blocks). The "Stop" sign gets so crowded with "dummy" signs that the robot can't tell where the real story ends.
The Solution: VoidPadding
The authors propose a simple fix called VoidPadding. They introduce a new, invisible token called [VOID].
Think of it like this:
- [VOID] is the new "dummy word." It fills the empty space on the practice page, but it has no meaning. It's like a ghost that takes up space but doesn't speak.
- [EOS] is now only the "Stop" sign. It is reserved strictly for telling the robot when the story is actually finished.
By separating these roles, the robot learns clearly:
- [VOID] = "This is just empty space, ignore it."
- [EOS] = "The story is done, stop now."
How It Works in Practice
The paper describes two clever tricks that happen during the "inference" (when the robot is actually doing the work):
- The "Ghost" Ban: When the robot is generating a story, it is strictly forbidden from writing [VOID]. If it tries to guess [VOID], the system says "No, that's just a ghost." This prevents the robot from accidentally filling its story with invisible ghosts.
- The Early Stop: Because [EOS] is now a pure "Stop" sign, the robot can listen to it. As soon as it sees a clear [EOS] signal, it stops writing immediately. It doesn't waste time filling out the rest of the page with garbage. This makes the robot much faster.
- The Canvas Expander: Sometimes the robot starts with a page that is too small for the story it wants to tell. The paper introduces a trick called VoidExpansion. The robot looks at the "ghost" signals ([VOID]) it learned during training. If the page is too short, the [VOID] signals will look "uncomfortable" (like a ghost trying to squeeze into a tiny box). The robot senses this, expands the page to a bigger size, and then finishes the story.
The Results
The authors tested this on two different robot models (LLaDA and Dream) using math and coding puzzles.
- Better Quality: When the robots tried to write long answers, the old method often failed and just spat out "End of Sentence" over and over. The new method (VoidPadding) solved this, keeping the answers long and correct.
- Faster: Because the robots stopped exactly when they were done (instead of filling the whole page), they finished tasks 55% faster on average.
- Robust: The new method worked well whether the robot was writing short answers or very long ones, and whether it was working in small chunks or big chunks.
Summary
The paper shows that by giving the "Stop" sign and the "Empty Space" filler two different names, we can stop the robot from getting confused. This makes the robot write better, stop at the right time, and work much faster. It's a small change in how we teach the robot that leads to a big improvement in how it performs.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.