Rockbox Development > New Ports
Cowon D2
Bkd11:
Well this might not be the proper forum to continue this discussion, but I ran tools/rockboxdev.sh selecting all options.
Then preceeded with tools/configure --no-eabi as you instructed.
--- Code: ---Normal build selected
Using source code root directory: /home/brian/rockbox
Using arm-elf-gcc 4.0.3 (400)
Using arm-elf-ld 2.16.1
--- End code ---
But still received same errors as in my post above. :(
mbk1969:
--- Quote from: funman on September 08, 2010, 11:03:57 PM ---EDIT: i don't think gcc support changing optimizations or other parameters through pragmas but if you know how i'd like to know
--- End quote ---
http://gcc.gnu.org/onlinedocs/gcc/Function-Specific-Option-Pragmas.html
:
#pragma GCC optimize ("string"...)
This pragma allows you to set global optimization options for functions defined later in the source file. One or more strings can be specified. Each function that is defined after this point will be as if attribute((optimize("STRING"))) was specified for that function. The parenthesis around the options is optional. See Function Attributes, for more information about the optimize attribute and the attribute syntax.
The `#pragma GCC optimize' pragma is not implemented in GCC versions earlier than 4.4.
http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function-Attributes
:
optimize
The optimize attribute is used to specify that a function is to be compiled with different optimization options than specified on the command line. Arguments can either be numbers or strings. Numbers are assumed to be an optimization level. Strings that begin with O are assumed to be an optimization option, while other options are assumed to be used with a -f prefix. You can also use the `#pragma GCC optimize' pragma to set the optimization options that affect more than one function. See Function Specific Option Pragmas, for details about the `#pragma GCC optimize' pragma.
This can be used for instance to have frequently executed functions compiled with more aggressive optimization options that produce faster and larger code, while other functions can be called with less aggressive options.
http://gcc.gnu.org/onlinedocs/gcc/ARM-Pragmas.html#ARM-Pragmas
torne:
Yes, it's possible, but the point you are missing is that GCC with no optimisations produces *spectacularly* wasteful code, since it doesn't generally bother to even keep local variables in registers... -O0 even for what you consider to be not-performance-critical code will generally turn out to be super slow...
shotofadds:
There's also no point in adding #pragmas to individual files, because once you have figured out which file(s) to change, you might as well solve the problem properly rather than working around it. Don't fret, it will get fixed soon enough.
Also note, the D2 build no longer works "out of the box" with the --no-eabi option (for a different reason to without Bkd11's errors): you also need to disable use of IRAM in apps/codecs/libmad/mad_iram.h.
AsusFreak:
Hi all.
By the way: an old problem came back I think:
r28058 does not start anymore. Only the bootloader is shown then i get the blackscreen and have to wait some minutes before being able to boot into OF.
We had a same issue some weeks ago (see closed FS#11558).
My last actual working build is r28051.
See FS#11618:
http://www.rockbox.org/tracker/task/11618
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version