Displaying 3 results from an estimated 3 matches for "mips5".
Did you mean:
mips
2019 Nov 13
3
Understanding targets
The term "target" is somewhat overloaded.
When llvm-config tells you it was built with the X86 target, that actually includes a variety of closely related architectures, such as x86_64, i386, and so on. Within the x86_64 architecture, there are many individual processor implementations that LLVM understands, such as Skylake, Bulldozer, and many many more.
What *clang* means by
2019 Nov 14
4
Understanding targets
Hello Paul and Simon, (Sorry - I'm not sure about the social conventions in mailing lists)
Both of your answers helped me a lot! So If I understand it correctly, Clang knows what 'mips1' and 'mips5' are - but can't generate code for it? Why is it like that?
I actually have a more in general questions about processors... If this is the wrong place for it, please ignore it, I'm just a bit confused.
So the R3000 is a "MIPS CPU"? What does that actually mean? Is the archite...
2015 May 15
3
[LLVMdev] MIPS asm backend emitting weird symbols into object file?
I'm cross-compiling for MIPS. The test-case is as simple as it can be:
void foo() {}
$clang -target mips64-octeon-linux -c -B
path/to/cross/compiled/mips/assembler a.c
And then I look at the object file:
$ nm a.o
0000000000000020 t $tmp0
0000000000000000 T foo
I would like to know what "$tmp0" is. Furthermore, if I pass -g to
clang, I see a whole bunch of such symbols. Some of