public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dan.naumov@ofw.fi
To: gcc-gnats@gcc.gnu.org
Subject: optimization/10030: gcc 3.2(.1) produces broken code with -O2, but not -O
Date: Tue, 11 Mar 2003 19:56:00 -0000	[thread overview]
Message-ID: <20030311195033.24350.qmail@sources.redhat.com> (raw)


>Number:         10030
>Category:       optimization
>Synopsis:       gcc 3.2(.1) produces broken code with -O2, but not -O
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 11 19:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Dan Naumov
>Release:        gcc version 3.2.1 [FreeBSD] 20021119 (release)
>Organization:
>Environment:
FreeBSD 5.0-p4
>Description:
When compiling AbiWord (http://www.abisource.com/) using CPUTYPE=athlon-tbird and CFLAGS= -O2 -pipe, the program compiles fine, but will always segfault upon exiting. Using -O instead solves the problem.
>How-To-Repeat:
1) obtain AbiWord 1.0.4
2) compile with -O2 and CPUTYPE=athlon-tbird
3) run and exit AbiWord
>Fix:

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


             reply	other threads:[~2003-03-11 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 19:56 dan.naumov [this message]
2003-03-11 20:11 bangerth
2003-03-26 10:24 ljrittle

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=20030311195033.24350.qmail@sources.redhat.com \
    --to=dan.naumov@ofw.fi \
    --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).