public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Matt.Rhodes@synergex.com To: gcc-gnats@gcc.gnu.org Subject: c/4596: GCC 3.0.1 optimization causes segmentation violation in executable Date: Wed, 17 Oct 2001 13:56:00 -0000 [thread overview] Message-ID: <20011017204641.23384.qmail@sourceware.cygnus.com> (raw) >Number: 4596 >Category: c >Synopsis: GCC 3.0.1 optimization causes segmentation violation in executable >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Wed Oct 17 13:56:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Matt Rhodes >Release: gcc version 3.0.1 >Organization: >Environment: Red Hat Linux 7.1 running on a Pentium 120. >Description: When the lcmdln.c module is compiled with -O3 optimization, the executable (dblibr) fails with a segmentation violation when it is run. However, when lcmdln.c is compiled with -O3 in addition to -fschedule-insns explicitly specified, the excutable runs without the segmentation violation. Also, it executes without error if lcmdln.c is only compiled with -O1 optimization. >How-To-Repeat: $ gcc -O3 -finline-functions -funroll-loops -fomit-frame-pointer -fexpensive-optimizations -fschedule-insns2 -fstrength-reduce -fno-strict-aliasing -trigraphs -march=pentium -fPIC -o lcmdln.o -c lcmdln.c $ gcc -o dblibr calloc.o lcreat.o lmain.o lmisc.o lcmdln.o lerrint.o nordisam.a duisam.a dutil.a stblib.a -lbsd -lm $ dblibr -c bldut.olb bldut1.dbo >Fix: Add -fschedule-insns to compiler options when building lcmdln.c module OR change -O3 compiler option to -O1. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-10-17 13:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-17 13:56 Matt.Rhodes [this message] 2001-11-14 13:26 rth 2001-11-14 15:16 rth
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=20011017204641.23384.qmail@sourceware.cygnus.com \ --to=matt.rhodes@synergex.com \ --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: linkBe 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).