From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19706 invoked by alias); 29 Dec 2002 20:46:43 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 19699 invoked from network); 29 Dec 2002 20:46:42 -0000 Received: from unknown (HELO caip.rutgers.edu) (128.6.236.10) by 209.249.29.67 with SMTP; 29 Dec 2002 20:46:42 -0000 Received: (from ghazi@localhost) by caip.rutgers.edu (8.9.3/8.9.3) id PAA04172; Sun, 29 Dec 2002 15:46:30 -0500 (EST) Date: Sun, 29 Dec 2002 16:41:00 -0000 From: "Kaveh R. Ghazi" Message-Id: <200212292046.PAA04172@caip.rutgers.edu> To: janis187@us.ibm.com Subject: Re: Analysis of g++.dg/bprob/g++-bprob-1.C multilib failures Cc: gcc@gcc.gnu.org References: <200212271716.MAA29305@caip.rutgers.edu> <200212281613.LAA12655@caip.rutgers.edu> <20021228182629.A22548@us.ibm.com> X-SW-Source: 2002-12/txt/msg01553.txt.bz2 > From: Janis Johnson > > On Sat, Dec 28, 2002 at 11:13:14AM -0500, Kaveh R. Ghazi wrote: > > > > 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. > Janis Thanks Janis, that'll be a big help. While you may be able to recreate the error with a multilib simulator, I suspect you may be able to use *any* multipass testsuite run. For example, one regular (plain vanilla) pass and one -fPIC pass. That would work on a native x86-linux-gnu box and should be much simpler since the cross stuff won't come into play. If you have the trunk already built and handy, as a first guess try: make RUNTESTFLAGS="--target_board 'unix{-fPIC,-fpic,}'" check-gcc-c++ see if that triggers it for you. Thanks, --Kaveh -- Kaveh R. Ghazi ghazi@caip.rutgers.edu