| --- Log opened Fri May 12 00:00:40 2017 | ||
| -!- blueCmd_ is now known as b | 08:59 | |
| -!- b is now known as blueCmd | 08:59 | |
| wbx | hi. what is the best supported gcc branch for openrisc? | 11:35 |
|---|---|---|
| ZipCPU | What are you hoping to accomplish? And which branches are you comparing between? | 12:03 |
| wbx | ZipCPU: stable builds for musl/uclibc-ng toolchains | 12:09 |
| wbx | https://github.com/openrisc/or1k-gcc | 12:10 |
| wbx | contains so many branches. at the moment I use musl-5.4.0 for everything | 12:10 |
| ZipCPU | You might wish to check GCC upstream. I think they've managed to merge all of their GCC changes into GCC proper. | 12:20 |
| wbx | ZipCPU: no. | 14:10 |
| wbx | ZipCPU: upstream doesn't contain openrisc support | 14:11 |
| ZipCPU | wbx: Let's see if one of the GCC developers has an answer for you --- they tend not to work in my time-zone. | 14:26 |
| shorne | wbx: musl-5.4.0 should be most up to date | 18:10 |
| shorne | or or1k-5.4.0 (musl has some extra defaults for musl, not so sure why we need 2) | 18:10 |
| shorne | the branches are just the releases | 18:10 |
| shorne | we should use tags I guess | 18:11 |
| shorne | wbx: actually musl-5.4.0 is a bit old | 18:12 |
| shorne | no, nevermind its fine | 18:14 |
| shorne | question with iverilog I am getting, Found both default and `timescale based delays. Use | 18:20 |
| shorne | ... | 18:20 |
| shorne | This is on one of my own modules, I dont see this using fusesoc on the orpsoc-core modules. | 18:20 |
| shorne | but it seems the issue would be the same | 18:20 |
| shorne | anyone know why the timescale warning doesnt come when I test things like wb_sdram_ctrl, even though none of the wb_sdram_ctrl modules have a timescale defined? | 18:25 |
| --- Log closed Sat May 13 00:00:41 2017 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!