Skip to main content
17 events
when toggle format what by license comment
Jan 12, 2020 at 9:35 answer added Bruce Abbott timeline score: 0
Jan 12, 2020 at 7:14 comment added Bruce Abbott Your new code has the same problem as the old code:- val and data are not used so they will be optimized away.
S Jan 12, 2020 at 6:53 history suggested Peter Mortensen CC BY-SA 4.0
Copy edited. Fixed the question formation - missing auxiliary (or helping) verb - see e.g. <https://www.youtube.com/watch?v=t4yWEt0OSpg&t=1m49s> (see also <https://www.youtube.com/watch?v=kS5NfSzXfrI> (QUASM)). Fixed the indentation (including for use in a Markdown list).
Jan 11, 2020 at 13:42 review Suggested edits
S Jan 12, 2020 at 6:53
Jan 10, 2020 at 10:25 comment added Mast Have you tried a hardware profiler to measure instead of estimate?
Jan 10, 2020 at 1:44 answer added Oldfart timeline score: 11
Jan 10, 2020 at 1:13 history edited ty_1917 CC BY-SA 4.0
added 665 characters in body
Jan 10, 2020 at 0:16 answer added yar timeline score: 14
Jan 10, 2020 at 0:00 history tweeted twitter.com/StackElectronix/status/1215423202916274176
Jan 9, 2020 at 21:05 comment added The Photon You can write your code as just val = ((PIND & (1 << PIND6)) == (1 << PIND6));, or val = ((PIND >> PIND6) & 1); (and probably a bunch of other ways). You should look at your compiler output to see whether you get different assembly code in each case and which one is fastest.
Jan 9, 2020 at 19:08 history became hot network question
Jan 9, 2020 at 12:10 comment added Criticizing Israel not allowed I expect this will capture the digital input state correctly, every time it runs, at any frequency. The question is, how often can you run this code?
S Jan 9, 2020 at 12:03 history suggested Mike CC BY-SA 4.0
I try to format the code
Jan 9, 2020 at 11:50 review Suggested edits
S Jan 9, 2020 at 12:03
Jan 9, 2020 at 11:35 answer added Curd timeline score: 8
Jan 9, 2020 at 11:08 answer added Swedgin timeline score: 22
Jan 9, 2020 at 11:00 history asked ty_1917 CC BY-SA 4.0