On 24.02.11 19:27, Christian Grössler wrote:
On 24.02.11 15:38, Jean-Marc Saffroy wrote:
On 02/23/2011 09:52 PM, Christian Grössler wrote:
Hello,
I have a problem with register allocation. Our architecture has some
pointer registers "pX" (24bit)
and some data registers "dX&
On 24.02.11 15:38, Jean-Marc Saffroy wrote:
On 02/23/2011 09:52 PM, Christian Grössler wrote:
Hello,
I have a problem with register allocation. Our architecture has some
pointer registers "pX" (24bit)
and some data registers "dX" (32bit). Since pointers are only 24bit,
we&
Hello,
I have a problem with register allocation. Our architecture has some pointer registers
"pX" (24bit)
and some data registers "dX" (32bit). Since pointers are only 24bit, we're
using PSImode for them.
There are restrictions in the "add" opcode, we can do
pX = add(pX,)
pX = add(pX,dX)
pX
On 19.02.11 23:01, Richard Guenther wrote:
On Sat, Feb 19, 2011 at 10:53 PM, Christian Grössler
wrote:
The failures come from the assembler which complains about the out of range
shift counts.
Should I disable them or is there any reason unknown to me that these tests
make sense?
You need
Hi,
I'm running the testsuite with a compiler for a private target.
I get many failures because of shift counts out of range (too big or negative).
Examples of failed tests:
gcc.c-torture/compile/20020710-1.c
gcc.c-torture/compile/20021119-1.c
gcc.c-torture/compile/20021124-1.c
The failures c
Hi,
I'm in the process of reviving a 2 year old port and merge the changes done to
gcc since Nov-2008 into it.
Now I'm getting an assertion failure:
In file included from ../../../src/libiberty/regex.c:638:0:
../../../src/libiberty/regex.c: In function 'byte_re_match_2_internal':
../../../src/
Hello Ian,
On 28.12.10 06:37, Ian Lance Taylor wrote:
Seems like you don't have a cbranchMODE4 insn in the required mode.
Double check that. You should only get to that assert if there is no
cbranch pattern. To assert is indicating that if there is no cbranch
pattern there has to be a cmp patt
On 28.12.10 00:22, Ian Lance Taylor wrote:
Christian Grössler writes:
Looking at the history of optabs.c, the MODE_CC test was introduced when
merging the cond-optab branch
to main. I didn't find a description of the cond-optab branch and what it was
supposed to do.
This i
Hello,
I'm trying to make a port to a new architecture work on the current gcc. There
hasn't been any work
done on this port since Nov-2008.
The compiler builds now, but I'm getting an ICE when I try to compile a program.
-
X:
--
(mem/f/c/i:PSI (plus:PSI (reg/f:PSI 87 virtual-stack-var
