public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pdl@la.utexas.edu
To: gcc-gnats@gcc.gnu.org
Subject: optimization/2927: gcc build of xemacs 21.1.14 core dumps with -O3 but not with -O2
Date: Thu, 24 May 2001 10:36:00 -0000	[thread overview]
Message-ID: <20010524172612.21003.qmail@sourceware.cygnus.com> (raw)

>Number:         2927
>Category:       optimization
>Synopsis:       gcc build of xemacs 21.1.14 core dumps with -O3 but not with -O2
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu May 24 10:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     pdl@la.utexas.edu
>Release:        gcc snapshot for 14-May-2001
>Organization:
>Environment:
Solaris 2.6, X Windows 11 R6.3, GNU ld, Ultra Sparc 2-300
>Description:
The default build configuration for Xemacs version 21.1.14
includes -O3. When I tried to build xemacs we got as far
as linking the temacs binary, but then that binary core
dumped with a bus error when it tried to load up the
initial elisp code. I reduced the optimization level to
-O2 and this problem went away, and the build of xemacs
completed without error.

This is basically an FYI rather than a bug report. The 
problem could be a matter of incorrect code in 
xemacs 21.1.14, a problem with the current version of
GNU ld as built on Solaris 2.6, or a problem in the
gcc optimizer. I suspect that it will be very difficult
to duplicate this problem :-) You would need a Solaris 2.6
ultra sparc box with the same set of OS patches as we have
installed, version R6.3 of X11 built with gcc 2.95, gcc
snapshot 14-May-2001 compiled with gcc snapshot 7-Mar-2001,
and etc.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-24 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24 10:36 pdl [this message]
2001-12-27 11:31 rodrigc
2002-01-17 22:05 rodrigc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010524172612.21003.qmail@sourceware.cygnus.com \
    --to=pdl@la.utexas.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).