| stekern | blueCmd: the regression tests went by with no new regressions, so I've pulled in your patches now | 09:27 |
|---|---|---|
| blueCmd | stekern: cool, did it fix anything? :P | 10:15 |
| stekern | gcc and g++ tests where exactly the same | 10:59 |
| stekern | libstdc++ tests have always failed to even start, they seem to be working now | 10:59 |
| stekern | ....but some test ran out of mem so it didn't run to the end | 11:01 |
| stekern | I'm going to increase the memory on it and rerun | 11:01 |
| stekern | blueCmd: here's the results if you want to take a look: http://oompa.chokladfabriken.org/tmp/regression/ | 11:04 |
| blueCmd | stekern: cool | 11:05 |
| stekern | gcc/gcc.log gcc/gcc.sum and g++/g++.log g++/g++.sum are the files that are of most interest | 11:05 |
| blueCmd | hah, omg the number of tests | 11:06 |
| stekern | yeah, 47/78324 isn't that bad after all ;) | 11:07 |
| blueCmd | hehe, i guess. | 11:07 |
| stekern | target is of course 0 | 11:10 |
| blueCmd | stekern: you don't happen to know if there has been any discussion about using/not using foo@X syntax for GAS? | 11:15 |
| blueCmd | I'm working on TLS for openrisc, and I need to introduce a couple of relocs, and right not i'm thinking about using ".long foo@tlsgd" | 11:16 |
| stekern | I used the plt(foo), got(foo) just because that was easiest to implement | 11:33 |
| stekern | in contrary to foo@plt | 11:35 |
| blueCmd | ah, I see. I will try that | 11:36 |
| blueCmd | because this @ is quickly turining to be quite intrusive | 11:36 |
| blueCmd | stekern: I'm trying to regenerate the cgen opcodes. I've read README-OR1K but I got stuck at this part: http://pastebin.com/41JYL4kJ | 12:26 |
| stekern | blueCmd: oh, we ought to remove that README-OR1K... it's outdated... | 13:37 |
| stekern | just configure or1k-src with --enable-cgen-maint | 13:37 |
| stekern | and the cgen stuff will be regenerated when you make | 13:37 |
| blueCmd | ah | 13:38 |
| blueCmd | nice | 13:38 |
| stekern | sorry bout the confusion :( | 13:38 |
| blueCmd | np :) | 13:38 |
| blueCmd | global offset table thread pointer offset high - gottpoffhi | 13:39 |
| blueCmd | nameing things is hard :P | 13:39 |
| blueCmd | naming* | 13:40 |
| * Xark links to a handy utility -> http://www.rinkworks.com/namegen/ :-) | 13:45 | |
| blueCmd | haha, Ghaskelang is a much better name - I agree | 13:45 |
| Xark | Hey, worked for Tolkien. :) | 13:46 |
| blueCmd | l.lwz r3,gottpofflo(foo)(r10) | 13:49 |
| blueCmd | that doesn't look neat | 13:50 |
| Xark | It is going to be tough to come up with an intuitive name for that... make sure to add a comment on its definition. :) | 13:58 |
| Xark | Maybe an underscore or two would help (if it fits with the style)... | 13:59 |
| blueCmd | heh, well it's called gottpoff in almost every other arch so I will stick to that | 13:59 |
| Xark | Excellent reasoning. :) | 13:59 |
| blueCmd | I wanted to do hi(gottpoff(foo)) first, but that wouldn't go with the other (gotoffhi / gotofflo) already existing ones | 13:59 |
| Xark | Yeah. For things like this I think consistency with other archs trumps "aesthetic concerns". | 14:00 |
| blueCmd | http://pastebin.com/1RaEdWVk woohoo my first relocations! \o/ | 14:04 |
| Xark | Nice. Working on TLS (or just general linker stuff)? | 14:05 |
| blueCmd | TLS, I want to port eglibc to openrisc | 14:05 |
| blueCmd | and the recommendation from the glibc guys at #glibc was that I s | 14:06 |
| blueCmd | should implement TLS first | 14:06 |
| blueCmd | (I have some compilation dependecy loops with emutls that GCC uses which I hope this will solve) | 14:06 |
| Xark | I see. Makes sense, as I can see it being a prerequisite. | 14:07 |
| stekern | blueCmd: nice progress! | 15:03 |
| stekern | blueCmd _franck_, I've added you to the "GNU toolchain" openrisc github team | 15:07 |
| stekern | _franck_: so once you are happy with your gdb work, feel free to push that | 15:08 |
| blueCmd | stekern: cool | 15:12 |
| stekern | now if I only could get this immu stuff working... | 15:34 |
| _franck_ | thanks stekern | 15:45 |
| _franck_ | I just wanted to run the regression test on it | 15:45 |
| _franck_ | however, I'm an expert and it's not my cup of tea... | 15:46 |
| _franck_ | so if someone can try to run the testsuite I'd be more than happy :) | 15:47 |
| _franck_ | https://github.com/Franck79/or1k-src/tree/prepare_patch | 15:47 |
| blueCmd | _franck_: ah, gdb - great! I will need gdb soon. | 17:13 |
| blueCmd | how do you use gdb? native via simulator, qemu or something else? | 17:14 |
| _franck_ | I'm using it with openocd server | 17:35 |
| stekern | blueCmd: for toolchain debugging, I recommend using or1ksim and it's tracing facility | 19:13 |
| blueCmd | stekern: I never got the tracing to work as I want | 19:32 |
| blueCmd | the disasm says that the instructions it's executing are invalid and stuff like that | 19:33 |
| blueCmd | maybe I have a faulty version of or1ksim | 19:33 |
| stekern | blueCmd: probably things that are still not fixed on 64-bit | 20:09 |
| stekern | I've got a 32-bit version I'm using | 20:09 |
| blueCmd | aha | 20:10 |
| stekern | it should really use the opcode library though, but that hasn't happened yet | 20:10 |
| stekern | I think it has some stuff copied from bfd into it | 20:10 |
| blueCmd | anyway, my GCC is now generating TLS code, the assembler is creating reloc "targets" or whatnot for it and marking the symbols for TLS | 20:11 |
| blueCmd | this is fun! I need to figure out why -O makes gcc forget about TLS though | 20:11 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!