Franck__ | as I'm not a toochain/gcc expert, could you tell me why I get a __muldi3 not defined with the or32 compiler ? | 01:14 |
---|---|---|
Franck__ | until now I used a libgcc.c file with those function | 01:15 |
Franck__ | but it seems I have a problem with u64 arithmetic using the libgcc I have in my barebox arch subdir | 01:15 |
Franck__ | I thought those arithmetics function are provided by gcc.... | 01:16 |
Jia | hi all | 07:11 |
Jia | when I run Linux using or1ksim | 07:11 |
Jia | it stoped at "Configuring loopback device" | 07:11 |
Jia | and no xterm startup. | 07:12 |
Jia | channel = "tcp:10084" | 07:28 |
Jia | channel = | 07:28 |
Jia | xterm | 07:28 |
juliusb | Franck_: Those _muldi3 functions should indeed by in libgcc | 10:24 |
juliusb | so double check that your toolchain is installed correclty and you're not using -nostdlib or something | 10:24 |
Franck_ | ok, I'll double check tonight | 12:44 |
Franck_ | however, I think I tried to compile in the ubuntu-virtualbox-image environment with the same result..... | 12:45 |
Franck_ | I'll tell you tonight | 12:45 |
juliusb | hmm odd | 13:35 |
juliusb | could you provide more information about what you're compiling and how? | 13:36 |
jonibo | Franck_: yes, muldi3 should be in libgcc... | 13:47 |
jonibo | however, I'm not sure that it's included if you build with "hardware" multiplication | 13:47 |
jonibo | hard-mul is the default... you need to specify soft-mul somewhere when building gcc to get those functions included | 13:47 |
Franck_ | jonibo: I tried with both hard-mul flag and without | 14:29 |
Franck_ | without the flag I have more unknown symbol | 14:30 |
Franck_ | with the flag some symbol left unresolved | 14:30 |
Franck_ | some more tests tonight.... | 14:31 |
juliusb | Franck_: can you then give us the compile line you're using? | 15:45 |
Franck_ | yeah I'll do when i'm back home :) I have some hardware to debug (at work :)) | 15:51 |
juliusb | np :) | 15:53 |
juliusb | where do yo work, mind if I ask? | 15:54 |
Franck_ | www.odyssee-systemes.fr, france | 15:56 |
Franck_ | hardware / low level soft / embedded system | 15:56 |
Franck_ | what about you ? | 15:57 |
juliusb | csr.com | 16:00 |
juliusb | doing digital design | 16:01 |
Franck_ | nice products | 16:03 |
Franck_ | your country ? | 16:09 |
juliusb | I'm Australian | 16:25 |
juliusb | but working here in Cambridge | 16:25 |
juliusb | so what is your interest in openrisc? are you interested for work or for play? | 16:32 |
Franck_ | just want to play with it | 16:35 |
Franck_ | I always have something to play with when my wife and boy are sleeping :) | 16:36 |
juliusb | haha | 16:37 |
juliusb | nice one | 16:37 |
Franck_ | I think what is really missing to openrisc is something like sopc builder (altera) | 16:37 |
juliusb | there's some other people like that in this project :) | 16:37 |
Franck_ | something to handle bus connection and arbitration | 16:37 |
juliusb | yes, well I'm looking at using IP-XACT for the project so we can have a better graphical frontened | 16:37 |
juliusb | and generate top-level and interconnect and arbiters | 16:37 |
Franck_ | exactly | 16:38 |
Franck_ | my next step (after barebox on simu) is to get an openrisc running on NEEK board (altera) | 16:38 |
juliusb | it will probably be my christmas project ;) | 16:39 |
Franck_ | then my be a software to have a sopc builder like | 16:39 |
juliusb | the neek board looks pretty cool | 16:39 |
juliusb | perfect for an OpenRISC system | 16:40 |
Franck_ | IP-XACT looks nice I didn't know it | 16:41 |
Franck_ | I'll take a look | 16:41 |
juliusb | enough RAM to run OS, ethernet, enough room for a design that will fit | 16:41 |
juliusb | do you know roughly how big barebox compiles to? is it < 128KB? | 16:42 |
juliusb | (the binary, of course) | 16:42 |
Franck_ | It depends how many features you want | 16:42 |
Franck_ | yo can have devfs, ramfs, hush shell | 16:43 |
Franck_ | for correct feature I'll say < 256K | 16:43 |
juliusb | cool KO | 16:44 |
juliusb | OK | 16:44 |
juliusb | sounds like a good stepping stone between u-boot and the Linux kernel | 16:44 |
Franck_ | my current nios barebox.bin is 120KB | 16:44 |
juliusb | oh yeah cool | 16:52 |
juliusb | that's about right | 17:00 |
juliusb | for a mini OS/bootloader for a 32-bit RISC CPU | 17:00 |
olofk_htc | jonibo: What's the plan for or1ksim.cfg in the kernel? I just saw that it wasn't in upstream | 18:01 |
Franck_ | I'm back to business | 23:04 |
Franck_ | I'm working in the openrisc virtualbox environment system | 23:05 |
Franck_ | this is an example of my gcc use: | 23:05 |
Franck_ | damn I can't paste it | 23:08 |
Franck_ | -Wp,-MD,fs/.devfs-core.o.d -nostdinc -isystem /opt/or32-new/lib/gcc/or32-elf/4.5.1-or32-1.0rc4/include -D__KERNEL__ -D__BAREBOX__ -Iinclude | 23:08 |
Franck_ | -I/home/openrisc/barebox/arch/openrisc/include -I/home/openrisc/barebox/arch/openrisc/include -include include/generated/autoconf.h -fno-builtin | 23:08 |
Franck_ | -ffreestanding -D__OR1K__ -ffixed-r10 -fno-strict-aliasing -mhard-mul -mhard-div -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Os -pipe -g | 23:08 |
Franck_ | -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(devfs_core)" -D"KBUILD_MODNAME=KBUILD_STR(devfs_core)" | 23:09 |
Franck_ | -c -o fs/devfs-core.o fs/devfs-core.c | 23:09 |
Franck_ | then the compilation fails with: | 23:09 |
Franck_ | undefined reference to `__muldi3' | 23:09 |
Franck_ | reference to `__ashldi3' | 23:10 |
Franck_ | undefined reference to `__lshrdi3' | 23:10 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!