Error in ira-color.c while bootstrap trunk

Hello, I get the following error while bootstrap trunk -r171713 on arm-linux-gnueabi configured with: ../gcc/configure --prefix=/home/eres/mainline/ build_armv7 --enable-checking --enable-languages=c --enable-bootstrap --with-arch=armv7-a --with-mode=thumb Thanks, Revital /home/eres/mainline/b

A question about handling debug_insn in schedulers

Hello, I wonder how the instruction scheduler deals with debug_insn? Looking at how SMS handles notes I wonder if this mechanism is adopted to handle debug_insn in other schedulers: notes are ignored during the scheduling procedure and are carefully placed before the instruction that follow them

Trunk bootstrup failure with SMS flags

Hello, Recent trunk (-r174631) is broken when bootstrap it with SMS flags on ARM (configured with --with-arch=armv7-a). The last version of trunk that I'm aware of that passes bootsrap with SMS flags is 173786. Unfortunately I still can not put my finger on the cause for this fail and I begin to

Bootstrap failure on PowerPC

Hello, I get the following bootstrap failure on ppc64-redhat-linux with trunk -r174840 compiling with -O2 flag.. Thanks, Revital /bin/sh ../../libtool --tag=CC --mode=compile /home/eres/mainline/build/./gcc/xgcc -B/home/eres/mainline/build/./gcc/ -B/home/eres/mainline/build/powerpc64-unknown-

Re: Bootstrap failure on PowerPC

Hello, > > Can you provide a backtrace and open a bugreport? Sure, will do that. (I deleted the bootstrap dir so I can not provide that info immediately though) Thanks, Revital

Bootstrap failure with doloop optimization on ARM

Hello, Trunk currently fails to bootstrap with SMS flags on ARM machine. (I'm using -r175900. btw, -r175091 bootstrap OK) Investigating the problem; it seems that the cause is not related to SMS but rather to the doloop optimization which is enabled only when SMS flags are set. (but that also does

A question about sched_analyze_insn in sched-deps.c

Hello, I appriciate explanation regarding the following piece of code in sched_analyze_insn function (sched-deps.c): When handling jump instruction dependence edges are created between the jump instruction and memory writes and volatile reads and I'm not quite sure the reason why. Thanks, Revital

Re: A question about sched_analyze_insn in sched-deps.c

Hello, >> I appriciate explanation regarding the following piece of code in >> sched_analyze_insn function (sched-deps.c): When handling jump instruction >> dependence edges are created between the jump instruction and memory >> writes and volatile reads and I'm not quite sure the reason why. > >

A question abt finding all register uses in instruction

Hello, I am trying to extract the regsiter uses in instructions using note_uses function. When encountering the following instruction I do not get r479 as a use; seemingly because of the following in note_use function: if (GET_CODE (dest) == ZERO_EXTRACT) { (*fun) (&X

Question abt getting the number of available registers

Hello, I'm working on estimating register pressure in SMS and using ira_available_class_regs for getting the number of available registers. However I encounter a case where ira_available_class_regs showed 64 available regs for a certain class while ira_class_hard_regs_num showed 61 so I am not sur