Displaying 5 results from an estimated 5 matches for "medany".
Did you mean:
meany
2012 Dec 04
2
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2012-12-04 23:10:18 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-04 23:10:18 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-04 23:10:18 - starting RELENG_8 tinderbox run for sparc64/sparc64
TB --- 2012-12-04 23:10:18 - cleaning
2020 Mar 27
3
llvm-objdump cannot recognize mul&mulh RISC-V M Instructions
...ALL_PREFIX="/home/llvm/workspace/riscv/riscv-tc-20200220"
-DLLVM_DEFAULT_TARGET_TRIPLE="riscv32-unknown-elf"
-DLLVM_ENABLE_PROJECTS="clang;lld;libc" -DLLVM_TARGETS_TO_BUILD="RISCV"
../llvm
```
Instructions to compile and dump:
```
RISCV_GCC_OPTS ?= -mcmodel=medany -static -O3 -std=gnu99 -fno-common
-fno-builtin -march=rv32im -mabi=ilp32 -DMB_ADDR=0x80FFFFC
--target=riscv64-unknown-elf
--sysroot=/home/llvm/workspace/riscv/riscv-tc-20200220/bin/riscv64-unknown-elf
--gcc-toolchain=/home/llvm/workspace/riscv/riscv-tc-20200220
RISCV_LINK_OPTS ?= -static -nostdlib...
2020 Mar 20
2
RISC-V LLVM sync-up call 19 Mar 2020
...ad only data in ROM. Besides the obvious case of addressing, say, a peripheral buffer in a distant memory location. But the scheme above would not allow code and data to reside in different memory devices, if the user so prefers.
On the other hand, just like we have the code models `medlow` and `medany`, we could have two variations of the compact code model too. One assuming that code and small data and local data are on the same memory device (`cmplow`) and another assuming no such restriction (`cmpany`).
Thank you,
__
Evandro Menezes ◊ SiFive ◊ Austin, TX
From: llvm-dev <llvm-dev-bounc...
2020 Mar 23
2
RISC-V LLVM sync-up call 19 Mar 2020
...M. Besides the obvious case of addressing, say, a peripheral buffer in a distant memory location. But the scheme above would not allow code and data to reside in different memory devices, if the user so prefers.
>>
>> On the other hand, just like we have the code models `medlow` and `medany`, we could have two variations of the compact code model too. One assuming that code and small data and local data are on the same memory device (`cmplow`) and another assuming no such restriction (`cmpany`).
>>
>> Thank you,
>>
>> __
>> Evandro Menezes ◊ SiFive ◊...
2020 Mar 20
2
RISC-V LLVM sync-up call 19 Mar 2020
If I’m following correctly, there are two size-limited areas. One area, limited to 2GB, is the “text” area. This contains all the code. Then there’s a “global” area, limited to 4GB, which is pointed to by the global pointer. This contains the GOT, plus a flexible area that the object file can stick small bits of data into. And then outside of both of those, additional data is unlimited.
It