| stekern | juliusb: the problem that the patch solves is that the timer exception wasn't turned off when the test was done, so the exception had time to hit once more (increasing the test counter) before the final test code was run | 02:50 |
|---|---|---|
| stekern | "uncommon that you have much between your code and the processor" <- what does that mean? | 02:51 |
| stekern | little abstraction in your application? | 02:52 |
| olofk | First patches since christmas applied for orpsocv3. Can't take credit for any of the work though | 03:04 |
| juliusb | ohhh ok, I get it | 12:17 |
| juliusb | (regarding timer test) | 12:18 |
| juliusb | um,by the "uncommon" comment, I meant it's usually not the case that you have a lot of stuff on the instruction fetch bus of the processor | 12:19 |
| juliusb | you couple it as closely as possible to where the instructions are coming from, or you put in a nice cache | 12:19 |
| juliusb | but in deeply embedded stuff you've got a ROM or a biggish RAM, so just put it as closely as possible to that | 12:19 |
| juliusb | anyone know how to get the name of the recipe/target being run in Make as a variable? | 14:42 |
| juliusb | like, to alter a variable if we're running a particular target? | 14:43 |
| juliusb | so the name of thing you pass to Make, ie. "make foo" I want to know how to test if one of the recipes we're going to run is foo | 14:44 |
| juliusb | MAKECMDGOALS is it i believe | 14:48 |
| blueCmd | _franck_: great! | 15:40 |
| stekern | juliusb: ah, ok. Yeah, that makes sense, and is kind of expected, I mean, why waste logic on some biu and fetch stall logic if you're going to run from a fast easily determinable ROM | 16:58 |
| juliusb | Ok I think I have carry and overflow logic working in espresso and prontoespresso | 17:21 |
| juliusb | I think I'll push that for now | 17:22 |
| stekern | I assume you have some tests for it? I can take a look at adding it to cappuccino | 17:24 |
| juliusb | no just coded it up, testing? why bother testing? ;) | 17:24 |
| stekern | :) | 17:24 |
| juliusb | haha yes | 17:24 |
| juliusb | a overflow and carry test, plus a test written in C which will generate random numbers, test if they should generate overflow or carry and then do them in hardware | 17:25 |
| juliusb | and check the results | 17:25 |
| juliusb | i pushed that last night to mor1kx-dev-env | 17:25 |
| juliusb | wel, the fancy test anyone, but I have more to push today | 17:25 |
| juliusb | s/anyone/anyway/ | 17:25 |
| juliusb | noticed a discrepency between my implementation in espresso and pronto for the overflow exception stuff - on one the result was written to the RF, but in the other the result was not. I think it's sensible to write the result, so I've done that | 17:27 |
| juliusb | but that made me think more about the software doing the resting | 17:27 |
| juliusb | testing | 17:27 |
| juliusb | which is good, so anyone, I'm reasonably sure it's robust | 17:27 |
| stekern | I'm making slow progress with everything atm now though, busy with laying in the sun and bathing ;) | 17:27 |
| stekern | so only hack a bit to the morning coffee and the night cap beer | 17:28 |
| juliusb | it only does it for add, though, my brain broke when I tried to figure out how l.sub should work | 17:28 |
| juliusb | oh where are you? | 17:28 |
| stekern | thailand | 17:28 |
| juliusb | somewhre sunny I hope | 17:28 |
| juliusb | and not finland | 17:28 |
| juliusb | oh nice! :) | 17:28 |
| juliusb | i see it's a bit of a night-hack for you at the moment then | 17:28 |
| stekern | we're making the escape from snow-hell a yearly event ;) | 17:28 |
| stekern | yeah, half past ten here | 17:29 |
| juliusb | good call. I've had to do it every year I've been here in norther europe | 17:30 |
| juliusb | brings you back to life :) | 17:30 |
| stekern | (written to rf) I'm not sure what you meant there, but I've just made some changes to cappuccino that cuts all wb off on exception | 17:33 |
| stekern | s | 17:33 |
| stekern | i.e. it also flushes the tail of the pipeline | 17:33 |
| juliusb | well, for range i think it's obvious that you want to keep the result, you just also want to know if it caused a range exception too | 17:34 |
| stekern | I think taking all exceptions in the "ctrl" stage was a good call (you made that in fourstage already) | 17:34 |
| juliusb | sure, the result overflowed but you probably want both the result and the record of it overflowing, not one or the other | 17:35 |
| juliusb | ha yeah spreading out the exception handling logic everywhere would make it a nightmare | 17:36 |
| stekern | hmm, yes, that sounds right | 17:36 |
| juliusb | and allowing them to flow through makes things a little easier I think | 17:36 |
| juliusb | flow through from the earlier stages, that is | 17:36 |
| stekern | yes, that's exactly my point | 17:36 |
| stekern | just push in noops if they are detected early | 17:37 |
| juliusb | ya, too easy right? | 17:37 |
| juliusb | something that's less easy - tiger or singha? | 17:37 |
| juliusb | :) | 17:37 |
| juliusb | (don't say carslberg!) | 17:38 |
| stekern | yup, tlb miss exceptions coupled with ibus errors etc have not caused me any head aches at all ;) | 17:38 |
| stekern | nah, I didn't even drink any carlsberg when I was in copenhagen last month | 17:38 |
| stekern | I think I prefer Chang the most, but it's pretty watery... but what's not here | 17:39 |
| juliusb | ah yes, chang | 17:40 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!