This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Record that immediate_operand & co. can accept HIGHs


On Fri, 2 May 2008, Richard Sandiford wrote:
> Tested in combination with the other patches by building
> cc1 and cc1plus for:
>
>     alpha-linux-gnu arc-elf arm-eabi avr-rtems bfin-elf cris-elf
>     fr30-elf frv-elf h8300-elf i686-linux-gnu x86_64-linux-gnu
>     iq2000-elf m32c-elf m32r-elf m68hc11-elf m68k-elf mcore-elf
>     mipsisa64-elf mmix-knuth-mmixware hppa2.0-linux-gnu pdp11-bsd
>     powerpc64-linux-gnu powerpc-linux-gnu s390-linux-gnu score-elf
>     sh-elf sh64-elf sparc-sun-solaris2.8 spu-elf xstormy16-elf
>     v850-elf vax-netbsdelf xtensa-elf
>
> and making sure that there were no changes in the assembly output for
> gcc.c-torture, gcc.dg and g++.dg (compiled once with -g and once with
> -O2).

If you meant you did that for each config above, how?
Using spark's -wrapper I presume, but how?

(I used to have a setup where I could do something like that,
but it has rotted.)

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]