This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Analysis of g++.dg/bprob/g++-bprob-1.C multilib failures
On Sat, Dec 28, 2002 at 06:26:29PM -0800, Janis Johnson wrote:
> On Sat, Dec 28, 2002 at 11:13:14AM -0500, Kaveh R. Ghazi wrote:
> > > > set perf_ext tim
> > >
> > > Since checking by running multilibs tests takes so long, I was hoping
> > > someone could comment on this and let me know if I'm on the right
> > > track.
> >
> > No luck, it didn't make a difference.
> >
> > I'm kind of stuck, since this is a maze of dejagnu stuff. If someone
> > has ideas I would appreciate some help on this one.
>
> I wrote the framework for those tests, so perhaps I could figure out
> what's going on. I've never used multilibs; is that something I could
> do with a cross compiler (and simulator) on my i686-pc-linux-gnu laptop
> while I'm at home during the next few days? It's cranking away looking
> for patches that introduced regressions, but it could be put to work
> doing something else for a while, and I can interrupt my weaving and
> papermaking and baking and lazing about to try to remember what those
> tests are doing.
Sure. Test any multilibbed target; I use SH. Try giving
RUNTESTFLAGS="--target_board sh-hms-sim{,2}" to test sh1 and sh2, if I
remember correctly.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer