--- Log opened Wed Nov 23 00:00:42 2016 | ||
--- Day changed Wed Nov 23 2016 | ||
olofk_ | shorne: This rebasing stuff seems to be a never ending story | 02:09 |
---|---|---|
mithro | Is anyone here going to 33C3? | 04:07 |
shorne | olofk_: thats why we need to get these changes upstream | 04:14 |
shorne | then I think it ends | 04:14 |
shorne | hope reviews go well | 04:14 |
shorne | I talked to the guy on #gdb working on the refactorings, he says its done. | 04:15 |
shorne | ill make the changes | 04:15 |
shorne | Done, and fixed now running gdb testsuite | 05:00 |
shorne | if its as good as before I will publish the patches to gdb list | 05:00 |
shorne | If not, ill have to work on fixing tests again | 05:01 |
shorne | https://gist.github.com/stffrdhrn/49f522336afa7ee1242ed871d2c06a39 | 05:31 |
shorne | results look good, a few more failures, (maybe new tests) a lot more passes | 05:31 |
shorne | If anyone uses gdb openrisc and wants to test check | 05:32 |
shorne | https://github.com/stffrdhrn/binutils-gdb/tree/or1k-upstream | 05:32 |
olofk_ | Great shorne. Don't have time right now to run the tests, but I will if I can. And keep us posted on the progress | 06:29 |
olofk_ | Got a a link to the list where the patches are? | 06:29 |
arand___ | Noob cache questions: With the data cache in or1.2k (8k/16b), if one wants to invalidate the whole cache, can one simply call DCBIR on the block number? So issuing it on 0x0 would work even though that's not the page from memory that happens to be cached at the moment? | 14:26 |
arand___ | Hmm, mixed two questions into one: 1. Can whole dcache be invalidated by calling DCBIR on 0x00, 0x10, .., 0x2000? 2. (And related) Does invalidate act on memory address or cache address? | 14:30 |
olofk_ | arand___: Haven't really looked into those parts of OpenRISC, but here's the function where caches are invalidated in newlib if that helps https://github.com/bminor/newlib/blob/master/libgloss/or1k/caches-asm.S#L120 | 16:05 |
shorne | olofk_: link to patches? i.e. https://github.com/stffrdhrn/binutils-gdb/commits/or1k-upstream ? | 16:42 |
shorne | or the git format-patch? | 16:42 |
shorne | I can send the mails to openrisc list first for review | 16:50 |
olofk_ | shorne: Ah ok. I misread you. Thought they were already submitted to the gdb mailing list | 17:02 |
olofk_ | Was just curious to see the status of the upstream review process | 17:03 |
shorne | ok, let me send now | 17:08 |
shorne | just wrote cover letters I will cc openrisc | 17:08 |
shorne | olofk_: you should have just been spammed | 17:11 |
shorne | ezmlm-reject: fatal: Sorry, I don't accept messages larger than 400000 bytes (#5.2.3) | 17:21 |
shorne | Subject: [PATCH 14/18] sim: or1k: Regenerate autotool files | 17:21 |
olofk_ | doh | 17:27 |
olofk_ | Does gdb keep the generated autotool files in the repo? | 17:28 |
olofk_ | got to sleep now, but I'm really excited about this. It's a major milestone | 17:28 |
ZipCPU | Wow! You didn't just spam olofk_ ... ;) | 17:37 |
@juliusb | shorne: nice wrork on the patches! | 17:51 |
@juliusb | and I'm wondering, does anyone have a link to an up-to-date build tutorial for an OpenRISC SoC on the Atlys board? | 17:52 |
shorne | juliusb: thanks, I dont have build instructions on an atlys board, but I do think I saw some people working on it. You will probably get a reply soon | 17:54 |
shorne | ZipCPU: sorry, hope people dont mind sending the patch sets for review to the list | 17:54 |
ZipCPU | shorne: That's fine. I'm just ... being vocal. (textual?) Besides, i'd like to get gdb up and running for the ZipCPU, and you've just given me something to study. | 17:56 |
--- Log closed Thu Nov 24 00:00:57 2016 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!