This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.0 Release Criteria
On Wed, May 03, 2000 at 04:54:31PM -0500, Robert Lipe wrote:
> It's true. I have one target that is "broken" when configured for
> i686 becuae the lame-o assembler doesn't grok P6 opcodes. (Note to
> myself: remember to make configure.in "dumb down" the triplet for this
> target since GAS isn't a viable option for it.)
Err.. that just means that -march=i686 won't work. But
configuring as i686-foo doesn't emit i686 opcodes, just
tunes instruction selection and scheduling.
> Is it enough to pick one well-exercised IA32 target and test it like
> RUNTESTFLAGS='--target_board{-mi386,-mi486,-mi586,-mi686,-mk6}'?
Yes, that's the same as varying configuration triple.
Adding -march=i686 to this list would be helpful as well.
It also expands enormously the time it takes to test. Which
is why I was hoping to distribute the load a bit...
r~