2 msgBest of luck for GSoC 2007 participants!
4 msganyone using svk?
2 msgFW: [M16C] : 20 bit data pointer
3 msgRe: Toolchain for Maverick Crunch FPU
5 msgRe : Problem with gcc 3.4.0 & 3.4.6 in ARM ...

peephole patterns are not matching
\ Mohamed Shafi (12 Apr 2007)
. \ Andreas Schwab (12 Apr 2007)
. . \ Mohamed Shafi (12 Apr 2007)
. \ Jim Wilson (12 Apr 2007)

2 msgProblem with gcc 3.4.0 & 3.4.6 in ARM thumb...
5 msgadding dependence from prefetch to load
8 msgRecent dataflow branch SPEC2000 benchmarking
1 msgPHI_NODE memory reduction, WAS: Re: RFC: GIMPLE...
4 msgA microoptimization of isnegative or greatertha...
68 msgRFC: GIMPLE tuples. Design and implementation p...
1 msggcc-4.1-20070409 is now available
2 msgRe: Integer overflow in operator new. Solved? E...
14 msgInclusion in an official release of a new throw...
5 msgGenerating RTL for function call sequences from...
11 msgRe: Integer overflow in operator new. Solved?
2 msgstatic symbol occurs twice in the executable.
4 msgMiscompilation...
1 msgVCG viewer...
Subject:peephole patterns are not matching
Group:Gcc
From:Mohamed Shafi
Date:12 Apr 2007


hello everyone,

I have the following 2 patterns which are consecutive. (from shorten
rtl dump file)

(insn 69 34 70 (set (reg:SQ 0 d0)
(reg:SQ 18 f2)) 79 {movsq} (nil)
(nil))

(insn 70 69 35 (set (reg:SQ 16 f0 [orig:38 D.3693 ] [38])
(reg:SQ 0 d0)) 79 {movsq} (nil)
(nil))


For the above pattern i wrote a peephole like this

(define_peephole
[(set (match_operand:SF 0 "data_reg" "=d")
(match_operand:SF 1 "float_reg" "f"))
(set (match_operand:SF 2 "float_reg" "=f")
(match_operand:SF 3 "data_reg" "d"))]
"REGNO(operands[0]) == REGNO(operands[3])"
"movf\\t%1, %3"
)

even i wrote define_peephole2 which is similar to the above.
But the above patterns are not matched at all. But i can find these
patterns in the rtl dumps.

What could be the reason for this behavior?

Regards,
Shafi


© 2004-2008 readlist.com