Statistics of Recompressing Videos

A social network for dogs called DH (DogHouse) has k special servers to recompress uploaded videos of cute cats. After each video is uploaded, it should be recompressed on one (any) of the servers, and only after that it can be saved in the social network.

We know that each server takes one second to recompress a one minute fragment. Thus, any server takes m seconds to recompress a m minute video.

We know the time when each of the n videos were uploaded to the network (in seconds starting from the moment all servers started working). All videos appear at different moments of time and they are recompressed in the order they appear. If some video appeared at time s, then its recompressing can start at that very moment, immediately. Some videos can await recompressing when all the servers are busy. In this case, as soon as a server is available, it immediately starts recompressing another video. The videos that await recompressing go in a queue. If by the moment the videos started being recompressed some servers are available, then any of them starts recompressing the video.

For each video find the moment it stops being recompressed.

The first line of the input contains integers n and k (1 ≤ n, k ≤ 5·10⁵) — the number of videos and servers, respectively.

Next n lines contain the descriptions of the videos as pairs of integers s_i, m_i (1 ≤ s_i, m_i ≤ 10⁹), where s_i is the time in seconds when the i-th video appeared and m_i is its duration in minutes. It is guaranteed that all the s_i's are distinct and the videos are given in the chronological order of upload, that is in the order of increasing s_i.

Print n numbers e₁, e₂, ..., e_n, where e_i is the time in seconds after the servers start working, when the i-th video will be recompressed.

3 2
1 5
2 5
3 5

6
7
11

6 1
1 1000000000
2 1000000000
3 1000000000
4 1000000000
5 1000000000
6 3

1000000001
2000000001
3000000001
4000000001
5000000001
5000000004