public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roger Faust <roger_faust@bluewin.ch>
To: gcc-help@gcc.gnu.org
Subject: Code Optimization
Date: Sun, 13 Jan 2002 15:19:00 -0000	[thread overview]
Message-ID: <02011404390300.00613@delta> (raw)

hi

can it be, that code optimization creates error (the manual doesn't seem to 
make it clear to me)? 
i'm quite sure, that the code is ok. it work allright, until i'm using 
optimization. then i'm getting a segmentation fault, with O1 and O2 on the 
same position, with O3 earlier. the postion doesn't help my much, because the 
line where the error occurs seems for me ok (one time it's a return statment 
from main, the other one a asignment) and refering to the manual, it doesn't 
has to be this line.
any tipps to track down the bugs?

i'm using gcc 2.95.2 on suse 7.1 and gcc 2.95.4 on debian woody where the 
error was both times the same

thanks
--
	Roger Faust

             reply	other threads:[~2002-01-13 23:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 15:19 Roger Faust [this message]
2013-08-07  6:01 code optimization hemant undale
2013-08-07  7:16 AW: " Christoph Kobe
2013-08-07  7:35 ` hemant undale

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=02011404390300.00613@delta \
    --to=roger_faust@bluewin.ch \
    --cc=gcc-help@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).