> But I'm not building for thumb, on the contrary, that code I'm
> compiling is performance sensitive and I don't want to use thumb at
> all.
> MS compilers are way behind gcc in this regard, the latest what they
> support is armv5e. But it doesn't mean that you can't use instructions
> supported by the CPU, right? How is that I'd have kernel issues then?
> The same way, I used arm6 code and it all worked without problems, this
> time I want to try to compile some code for snapdragon cpu (I have a
> couple devices), but it seems like gcc won't compile anything for the
> new instruction set.
> By the way... I don't really understand the details you provided
> regarding relocations. To me, when there is a dllimport function used,
> then in some imports section linker places a pointer to that function.
> That pointer is set by the loader at load time. Overall, the code:
>
> #include <windows.h>
> int main(int argc, char **argv){
> return (long) &VirtualAlloc;
> }
>
> In my understanding is identical to:
>
> static volatile const void * const __imp_VirtualAlloc;
> int main(int argc, char **argv){
> return (long) __imp_VirtualAlloc;
> }
>
> Test confirms, that it returns the same error. Can I somehow completely
> disable thumb/thumb2 and only use regular arm 32-bit instructions plus
> neon/simd instructions (the ones that I need to execute)
>
By the way, I didn't want to use cegcc 4.4.0 for one other reason also: it
produced bigger binary. I wanted to actually check what's going on, it's not
some 10% increase, it's more like 200% increase in my case. Stripped
avcodec.dll went from 1.8 to 4.5 MB. I checked contents of each of the
sections... and guess what, one of the sections is full of zeroes (it has a bit
of data at the beginning and the rest is zeroes); the size of that section is
2.4MB. Is that normal with latest gcc version??
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
