From owner-freebsd-current Tue Oct 22 7:46:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D134C37B401; Tue, 22 Oct 2002 07:46:23 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D963A43E77; Tue, 22 Oct 2002 07:46:22 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA02230; Tue, 22 Oct 2002 10:46:22 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9MEjqP07449; Tue, 22 Oct 2002 10:45:52 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15797.25760.427922.700729@grasshopper.cs.duke.edu> Date: Tue, 22 Oct 2002 10:45:52 -0400 (EDT) To: Ruslan Ermilov Cc: Alexander Kabaev , "David O'Brien" , current@FreeBSD.org Subject: Re: Groff problems (was Re: alpha tinderbox failure) In-Reply-To: <20021022142929.GB48398@sunbay.com> References: <200210210942.g9L9gLpM025724@beast.freebsd.org> <15796.17145.909288.498725@grasshopper.cs.duke.edu> <20021022142929.GB48398@sunbay.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > If you remove -fno-exceptions from gnu/usr.bin/groff/Makefile.inc and > recompile libgroff and groff, it seems to work (I did not check it > thoroughly). But I think this only has a side effect, because Groff > does not seem to have any exception code (please correct me if I am > wrong), and why the hell it should depend on -mcpu, if any? > Interesting. I wonder of the lack of exceptions is what's confusing ld? As to mpcu: On alphas, the compiler has more chance to make mistakes if its compiled for CPUs < ev56 which do not support byte/word instructions. In those cases, it needs to generate shifty/masky code to pull 8 and 16 bit values out of 32-bit loads and stores. This has a history of being more error prone. Eg, some complex ports work on stable at high optimization levels with -mcpu=ev56 which don't work without -mpcu. If we have to, we can always compile groff as -mcpu=ev56 because we emulate these instructions in the kernel on older machines. That would make groff run about like molases in January on older machines, though, as each byte/word instruction would generate an illegal instruction trap and that trap would be handled by the alpha trap handler.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message