From owner-freebsd-bugs  Sun Oct 19 09:46:23 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA18171
          for bugs-outgoing; Sun, 19 Oct 1997 09:46:23 -0700 (PDT)
          (envelope-from owner-freebsd-bugs)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18152;
          Sun, 19 Oct 1997 09:46:14 -0700 (PDT)
          (envelope-from joerg@FreeBSD.org)
From: Joerg Wunsch <joerg@FreeBSD.ORG>
Received: (from joerg@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id JAA03717;
	Sun, 19 Oct 1997 09:44:38 -0700 (PDT)
Date: Sun, 19 Oct 1997 09:44:38 -0700 (PDT)
Message-Id: <199710191644.JAA03717@freefall.freebsd.org>
To: markm@iafrica.com, joerg@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: gnu/4511
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Synopsis: GCC optimization broken with -m486?

State-Changed-From-To: open-closed
State-Changed-By: joerg
State-Changed-When: Sun Oct 19 18:42:25 MEST 1997
State-Changed-Why: 

-m486 itself ain't broken.  It's so simple that its effect can easily
be verified in the compiler sources (it uses a default padding of 4
bytes instead of 2, and replaces the `leave' with a mov and a pop
instruction -- that's all folks).

The bug itself (unles already fixed) is more likely in the shell, but
we need a method to reproduce it should it appear again.