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

Solve Day 08 #13

Merged
merged 11 commits into from
Dec 9, 2020
Merged

Solve Day 08 #13

merged 11 commits into from
Dec 9, 2020

Conversation

manuphatak
Copy link
Owner

@manuphatak manuphatak commented Dec 8, 2020

Day 8: Handheld Halting

Your flight to the major airline hub reaches cruising altitude without incident. While you consider checking the in-flight menu for one of those drinks that come with a little umbrella, you are interrupted by the kid sitting next to you.

Their handheld game console won't turn on! They ask if you can take a look.

You narrow the problem down to a strange infinite loop in the boot code (your puzzle input) of the device. You should be able to fix it, but first you need to be able to run the code in isolation.

The boot code is represented as a text file with one instruction per line of text. Each instruction consists of an operation ( acc , jmp , or nop ) and an argument (a signed number like +4 or -20 ).

  • acc increases or decreases a single global value called the accumulator by the value given in the argument. For example, acc +7 would increase the accumulator by 7. The accumulator starts at 0 . After an acc instruction, the instruction immediately below it is executed next.
  • jmp jumps to a new instruction relative to itself. The next instruction to execute is found using the argument as an offset from the jmp instruction; for example, jmp +2 would skip the next instruction, jmp +1 would continue to the instruction immediately below it, and jmp -20 would cause the instruction 20 lines above to be executed next.
  • nop stands for No OPeration - it does nothing. The instruction immediately below it is executed next.

For example, consider the following program:

nop +0
acc +1
jmp +4
acc +3
jmp -3
acc -99
acc +1
jmp -4
acc +6

These instructions are visited in this order:

nop +0  | 1
acc +1  | 2, 8(!)
jmp +4  | 3
acc +3  | 6
jmp -3  | 7
acc -99 |
acc +1  | 4
jmp -4  | 5
acc +6  |

First, the nop +0 does nothing. Then, the accumulator is increased from 0 to 1 ( acc +1 ) and jmp +4 sets the next instruction to the other acc +1 near the bottom. After it increases the accumulator from 1 to 2, jmp -4 executes, setting the next instruction to the only acc +3 . It sets the accumulator to 5, and jmp -3 causes the program to continue back at the first acc +1 .

This is an infinite loop : with this sequence of jumps, the program will run forever. The moment the program tries to run any instruction a second time, you know it will never terminate.

Immediately before the program would run an instruction a second time, the value in the accumulator is 5 .

Run your copy of the boot code. Immediately before any instruction is executed a second time, what value is in the accumulator?

Part Two

After some careful analysis, you believe that exactly one instruction is corrupted .

Somewhere in the program, either a jmp is supposed to be a nop , or a nop is supposed to be a jmp . (No acc instructions were harmed in the corruption of this boot code.)

The program is supposed to terminate by attempting to execute an instruction immediately after the last instruction in the file . By changing exactly one jmp or nop , you can repair the boot code and make it terminate correctly.

For example, consider the same program from above:

nop +0
acc +1
jmp +4
acc +3
jmp -3
acc -99
acc +1
jmp -4
acc +6

If you change the first instruction from nop +0 to jmp +0 , it would create a single-instruction infinite loop, never leaving that instruction. If you change almost any of the jmp instructions, the program will still eventually find another jmp instruction and loop forever.

However, if you change the second-to-last instruction (from jmp -4 to nop -4 ), the program terminates! The instructions are visited in this order:

nop +0  | 1
acc +1  | 2
jmp +4  | 3
acc +3  |
jmp -3  |
acc -99 |
acc +1  | 4
nop -4  | 5
acc +6  | 6

After the last instruction ( acc +6 ), the program terminates by attempting to run the instruction below the last instruction in the file. With this change, after the program terminates, the accumulator contains the value 8 ( acc +1 , acc +1 , acc +6 ).

Fix the program so that it terminates normally by changing exactly one jmp (to nop ) or nop (to jmp ). What is the value of the accumulator after the program terminates?

Link

https://adventofcode.com/2020/day/8

@codecov
Copy link

codecov bot commented Dec 8, 2020

Codecov Report

Merging #13 (4e228d3) into main (44586d8) will decrease coverage by 2.10%.
The diff coverage is 91.30%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
- Coverage   98.00%   95.89%   -2.11%     
==========================================
  Files          10       12       +2     
  Lines         100      146      +46     
  Branches        5        9       +4     
==========================================
+ Hits           98      140      +42     
- Misses          0        3       +3     
- Partials        2        3       +1     
Impacted Files Coverage Δ
src/Day08/Solution.hs 89.74% <89.74%> (ø)
src/Day08/Utils.hs 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 44586d8...4e228d3. Read the comment docs.

@manuphatak manuphatak merged commit 4dbdbd6 into main Dec 9, 2020
@manuphatak manuphatak deleted the day_08 branch December 9, 2020 05:09
manuphatak added a commit that referenced this pull request Dec 10, 2020
* origin/main:
  Solve Day 09 (#15)
  Fix lint checks and type checks on CI (#16)
  Solve Day 08 (#13)
@manuphatak manuphatak added the solution A solution to a problem label Dec 12, 2020
@manuphatak manuphatak self-assigned this Dec 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution A solution to a problem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant