public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dick_guertin at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/25791] -O2 execution fails, -O and -g work Date: Tue, 17 Jan 2006 19:01:00 -0000 [thread overview] Message-ID: <20060117190124.8391.qmail@sourceware.org> (raw) In-Reply-To: <bug-25791-12018@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from dick_guertin at yahoo dot com 2006-01-17 19:01 ------- First, I inherited this code from a co-worker who left the University. My assignment was to keep this code working because the University relies on it. Everything was fine until we went from 3.3.1 to 3.4.4, and then -O2 compilations of this code created a module that got execution failures. I've been trying to "debug", but even 'gdb' is having troubles. I don't know what "proprocessed source" is. All I have is true source. I don't know how to do a "native backtrack" on a sparc, but would be willing to learn. I do know how to use 'gdb' to "disas", examine variables, etc. If you don't have the time to track this, then help me do it. By the way, did you notice the -O2 and -g caused "next" executing linear (non-looping) statements to go like this: 3615, 3616, 3615, 3616, 3616, 3616, 3617, ...?? What's with that? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25791
next prev parent reply other threads:[~2006-01-17 19:01 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-15 7:02 [Bug c/25791] New: -O2 execution fails using 3.4.4, " dick_guertin at yahoo dot com 2006-01-15 10:01 ` [Bug c/25791] -O2 execution fails, " ebotcazou at gcc dot gnu dot org 2006-01-16 23:16 ` dick_guertin at yahoo dot com 2006-01-16 23:20 ` [Bug rtl-optimization/25791] " pinskia at gcc dot gnu dot org 2006-01-17 1:19 ` dick_guertin at yahoo dot com 2006-01-17 4:35 ` dick_guertin at yahoo dot com 2006-01-17 6:59 ` ebotcazou at gcc dot gnu dot org 2006-01-17 8:33 ` dick_guertin at yahoo dot com 2006-01-17 8:47 ` ebotcazou at gcc dot gnu dot org 2006-01-17 19:01 ` dick_guertin at yahoo dot com [this message] 2006-01-17 20:55 ` dick_guertin at yahoo dot com 2006-01-18 3:10 ` dick_guertin at yahoo dot com 2006-01-18 13:31 ` ebotcazou at gcc dot gnu dot org 2006-01-18 13:38 ` ebotcazou at gcc dot gnu dot org 2006-01-19 4:00 ` dick_guertin at yahoo dot com 2006-01-19 4:04 ` pinskia at gcc dot gnu dot org 2006-01-19 4:50 ` dick_guertin at yahoo dot com 2006-01-19 6:41 ` dick_guertin at yahoo dot com 2006-01-19 6:51 ` pinskia at gcc dot gnu dot org 2006-01-19 6:55 ` ebotcazou at gcc dot gnu dot org 2006-01-19 7:46 ` dick_guertin at yahoo dot com 2006-01-19 8:26 ` dick_guertin at yahoo dot com 2006-01-19 8:39 ` ebotcazou at gcc dot gnu dot org 2006-01-19 12:16 ` pinskia at gcc dot gnu dot org 2006-01-19 17:54 ` dick_guertin at yahoo dot com 2006-01-19 18:23 ` dick_guertin at yahoo dot com 2006-01-19 18:33 ` ebotcazou at gcc dot gnu dot org 2006-01-21 8:17 ` dick_guertin at yahoo dot com
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=20060117190124.8391.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).