Hi,
I'm currently working on upgrading the version of gcc we use for mobile game
development on the mophun platform from 3.0.3 to 3.4.6. I've run into a
problem related to __builtin_apply that I cannot solve and I don't really
know where to start looking.
For some background the virtual CPU we ta
although I'm sure it is my fault in some way... :-)
/Roland
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Eric Christopher
> Sent: Wednesday, May 31, 2006 23:50
> To: Roland Persson
> Cc: gcc@gcc.gnu.org
> Subject: Re
>
> Otherwise you also might want to look to moving to 4.1/2 as long as
> you're moving.
>
I've been thinking about that recently. The main reason I'm going for 3.4 is
that it's what I started with about a year ago. Since then I've had to work
on other things most of the time.
Going from 3.0.
Hi,
When I compile for my cpu, the port for which is fairly functional (almost
all testcases pass), I get the following warnings:
gcc -c -g -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long
-DHAVE_CONFIG_H-I. -Icp -I../.
Hi,
My target has some instructions that do not exactly match any predefined
pattern names. What is the correct way to get gcc to use them in code
generation?
For example, I have an add instruction that can add a 32-bit integer (with
or without sign extension) to a 64-bit operand and store the re
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Rask Ingemann Lambertsen
> Sent: Monday, June 26, 2006 19:25
> To: Roland Persson
> Cc: gcc@gcc.gnu.org
> Subject: Re: Matching of non-standard instructions
>
>
> In a
