Re: unrecognizable insn generated in plugin?

2019-05-31 Thread Tycho Andersen
On Fri, May 31, 2019 at 05:43:44PM +0200, Mark Brand wrote: > On Thu, May 30, 2019 at 9:26 PM Tycho Andersen wrote: > > > > Hi Andrew, > > > > On Thu, May 30, 2019 at 10:09:44AM -0700, Andrew Pinski wrote: > > > On Thu, May 30, 2019 at 10:01 AM Tycho Andersen wrote: > > > > > > > > Hi all, > > >

Re: unrecognizable insn generated in plugin?

2019-05-31 Thread Mark Brand via gcc
On Thu, May 30, 2019 at 9:26 PM Tycho Andersen wrote: > > Hi Andrew, > > On Thu, May 30, 2019 at 10:09:44AM -0700, Andrew Pinski wrote: > > On Thu, May 30, 2019 at 10:01 AM Tycho Andersen wrote: > > > > > > Hi all, > > > > > > I've been trying to implement an idea Andy suggested recently for > >

Re: unrecognizable insn generated in plugin?

2019-05-30 Thread Tycho Andersen
ER_REGNUM), > gen_rtx_MEM(DImode, gen_rtx_REG(DImode, HARD_FRAME_POINTER_REGNUM); > > But that might not work either, you might need some thing more. Yes, thanks. You're also right that I still see the same problem: kernel/seccomp.c: In function ‘seccomp_check_filter’: ker

Re: unrecognizable insn generated in plugin?

2019-05-30 Thread Andrew Pinski
e plugin completes successfully, but GCC complains later, > > kernel/seccomp.c: In function ‘seccomp_check_filter’: > kernel/seccomp.c:242:1: error: unrecognizable insn: > } > ^ > (insn 698 645 699 17 (xor:DI (reg:DI 6 bp) > (mem:DI (reg:DI 6 bp) [0 S8 A8])) "ke

unrecognizable insn generated in plugin?

2019-05-30 Thread Tycho Andersen
gen_rtx_MEM(DImode, gen_rtx_REG(DImode, HARD_FRAME_POINTER_REGNUM; The plugin completes successfully, but GCC complains later, kernel/seccomp.c: In function ‘seccomp_check_filter’: kernel/seccomp.c:242:1: error: unrecognizable insn: } ^ (insn 698 645 699 17 (xor:DI (reg:DI 6 bp)

Re: error: unrecognizable insn:

2014-05-17 Thread Jakub Jelinek
On Sat, May 17, 2014 at 06:13:56PM +0530, Umesh Kalappa wrote: > Dear All, > We are porting the gcc 4.8.1 for our private target . > The compiler pops up with below error . > > error: unrecognizable insn: > > (insn 22 21 32 6 (set (reg:HI 30 [ D.1532 ]) >

error: unrecognizable insn:

2014-05-17 Thread Umesh Kalappa
Dear All, We are porting the gcc 4.8.1 for our private target . The compiler pops up with below error . error: unrecognizable insn: (insn 22 21 32 6 (set (reg:HI 30 [ D.1532 ]) (plus:HI (symbol_ref:HI ("stringArray") ) (const_int -1 [0x]))) -1 (nil))

Re: unrecognizable insn.

2012-06-15 Thread Ian Lance Taylor
t;<32|arg1, arg2 > > but I got the following error: > ----- > fib.c:38:1: error: unrecognizable insn: > (insn 15 14 16 4 (set (reg:DI 100) > (ashift:DI (reg:DI 100) >

unrecognizable insn.

2012-06-15 Thread Feng LI
following error: - fib.c:38:1: error: unrecognizable insn: (insn 15 14 16 4 (set (reg:DI 100) (ashift:DI (reg:DI 100) (const_int 32 [0x20]))) fib.c:25 -1 (nil)) - Not sure why this happe

Re: porting gcc to new arch: unrecognizable insn

2010-08-02 Thread Gabor Kerenyi
> > If I understand correctly it complains about a move instruction where src > > memory location should be (reg22+reg23). My arch defines: > > #define MAX_REGS_PER_ADDRESS 1 > > the first pseudo reg is 13 > > > > I think the wording of the second sentence in the M_R_P_A documentation > (beginn

Re: porting gcc to new arch: unrecognizable insn

2010-08-02 Thread Dave Korn
On 01/08/2010 16:26, Gabor Kerenyi wrote: > I'm porting GCC 4.4.4 to a new arch and while cross-compiling libgcc I get > the > following error: > ../../../libgcc/../gcc/libgcc2.c: In function ‘__clzsi2’: > ../../../libgcc/../gcc/libgcc2.c:716: error: unrecognizable insn:

porting gcc to new arch: unrecognizable insn

2010-08-01 Thread Gabor Kerenyi
Hi All, I'm porting GCC 4.4.4 to a new arch and while cross-compiling libgcc I get the following error: ../../../libgcc/../gcc/libgcc2.c: In function ‘__clzsi2’: ../../../libgcc/../gcc/libgcc2.c:716: error: unrecognizable insn: (insn 49 48 50 16 ../../../libgcc/../gcc/libgcc2.c:713 (set (r

Re: unrecognizable insn ICE in latticemico32 (lm32-elf) when building Linux kernel

2010-05-25 Thread Ian Lance Taylor
Philip Pemberton writes: >> The address is unusual: >> >> (subreg:SI (mem/s:DI (plus:SI (reg/v/f:SI 39 [ ctx ]) >> (const_int 64 [0x40])) [0 S8 A64]) 4) >> >> Why isn't that simply >> >> (mem/s:SI (plus:SI (reg/v/f:SI 39 [ ctx ]) >> (const_int 68 [0x40]))

Re: unrecognizable insn ICE in latticemico32 (lm32-elf) when building Linux kernel

2010-05-25 Thread Philip Pemberton
On 25/05/10 06:06, Ian Lance Taylor wrote: The official list of maintainers is stored in the gcc source code in the file MAINTAINERS. Having said that, there is no maintainer listed for lm32. I assume that it must be, as you suggest, Jon Beniston. Yeah, I spotted that in SVN about five minute

Re: unrecognizable insn ICE in latticemico32 (lm32-elf) when building Linux kernel

2010-05-24 Thread Ian Lance Taylor
Philip Pemberton writes: > 1) Who's the current maintainer for the lm32 port? Jon Beniston? > I can't see anything on the gcc website that says definitively "target > X is maintained by $PERSON", and I really don't want to step on > his/her toes and start a flame war, turf war or any other kind o

unrecognizable insn ICE in latticemico32 (lm32-elf) when building Linux kernel

2010-05-24 Thread Philip Pemberton
/timerfd.c: In function ‘timerfd_poll’: fs/timerfd.c:105:1: error: unrecognizable insn: (insn 44 43 45 5 fs/timerfd.c:94 (set (reg:SI 68) (subreg:SI (mem/s:DI (plus:SI (reg/v/f:SI 39 [ ctx ]) (const_int 64 [0x40])) [0 S8 A64]) 4)) -1 (nil)) fs/timerfd.c:105:1: internal

Re: unrecognizable insn after adding clobbers

2010-05-18 Thread Dave Korn
On 18/05/2010 15:24, Paulo J. Matos wrote: > On Tue, May 18, 2010 at 3:26 PM, Dave Korn wrote: >>> This however causes an unrecognizable insn error during the compiler >>> runtime when I have TARGET_X defined. >>> I was expecting the clobbers not to influence the

Re: unrecognizable insn after adding clobbers

2010-05-18 Thread Paulo J. Matos
On Tue, May 18, 2010 at 3:26 PM, Dave Korn wrote: >> >> This however causes an unrecognizable insn error during the compiler >> runtime when I have TARGET_X defined. >> I was expecting the clobbers not to influence the recognition but it >> seems I was wrong. &g

Re: unrecognizable insn after adding clobbers

2010-05-18 Thread Dave Korn
;*call_value_complex" > [ > (set (match_operand 0 "" "") > (call (mem:QI (match_operand:HI 1 "callable_operand" "yY,i")) > (match_operand:QI 2 "immediate_operand" "i,i"))) > (clobber (match_

unrecognizable insn after adding clobbers

2010-05-18 Thread Paulo J. Matos
call(operands); // deals with op0, 1 and 2. }) (define_insn "*call_value_complex" [ (set (match_operand 0 "" "") (call (mem:QI (match_operand:HI 1 "callable_operand" "yY,i")) (match_operand:QI 2 "immediate_operand" &qu

Re: Lots of new test failures on trunk due to unrecognizable insn

2008-03-05 Thread Dominique Dhumieres
See my comments in PR33009. Dominique d'Humieres

Lots of new test failures on trunk due to unrecognizable insn

2008-03-05 Thread İsmail Dönmez
es/gcc/gcc/testsuite/gcc.c-torture/compile/pr11832.c:30: error: unrecognizable insn: (insn 177/Users/cartman/Sources/gcc/gcc/testsuite/gcc.c-torture/compile/pr11832.c:30: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http:

Re: sync_fetch_and_add creating unrecognizable insn

2007-08-29 Thread David Edelsohn
>>>>> Razya Ladelsky writes: Razya> When passing an address of a local variable as the first argument of Razya> 'sync_fetch_and_add' Razya> I get an error of unrecognizable insn. Razya> Does anyone know why that happens? Probably a mistake in the rs6000_emit_rsync() procedure. David

Re: sync_fetch_and_add creating unrecognizable insn

2007-08-29 Thread David Daney
Razya Ladelsky wrote: Hi, When passing an address of a local variable as the first argument of 'sync_fetch_and_add' I get an error of unrecognizable insn. For example, the test below (extracted from gcc.c-torture/compile/sync-1.c) fails on powerpc. If however, 'uc' w

sync_fetch_and_add creating unrecognizable insn

2007-08-29 Thread Razya Ladelsky
Hi, When passing an address of a local variable as the first argument of 'sync_fetch_and_add' I get an error of unrecognizable insn. For example, the test below (extracted from gcc.c-torture/compile/sync-1.c) fails on powerpc. If however, 'uc' was a global variable, th