public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "galtgendo at o2 dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39333] gcc 4.3.3 miscompiles when -finline-small-functions is used
Date: Tue, 03 Mar 2009 15:15:00 -0000 [thread overview]
Message-ID: <20090303151502.30323.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39333-15488@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from galtgendo at o2 dot pl 2009-03-03 15:15 -------
Changing those two to unsigned doesn't help (I have checked that
even before comment 8). Actually, I changed a few ints to unsigned
wherever it looked sane for this file and it still crashed.
What's more, '-O1' works and when I decided to go down the man page
and test by -fno-* all of the features listed as additionally
turned on by -O2
(-fthread-jumps -falign-functions -falign-jumps -falign-loops -falign-labels
-fcaller-saves -fcrossjumping -fcse-follow-jumps -fcse-skip-blocks
-fdelete-null-pointer-checks -fexpensive-optimizations -fgcse
-fgcse-lm -foptimize-sibling-calls -fpeephole2 -fregmove
-freorder-blocks -freorder-functions -frerun-cse-after-loop
-fsched-interblock -fsched-spec -fschedule-insns
-fschedule-insns2 -fstrict-aliasing -fstrict-overflow -ftree-pre
-ftree-vrp) neither of them worked on its own.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39333
next prev parent reply other threads:[~2009-03-03 15:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 18:18 [Bug c/39333] New: " galtgendo at o2 dot pl
2009-03-01 18:20 ` [Bug c/39333] " galtgendo at o2 dot pl
2009-03-02 13:52 ` [Bug middle-end/39333] " pinskia at gcc dot gnu dot org
2009-03-02 21:56 ` galtgendo at o2 dot pl
2009-03-02 22:20 ` galtgendo at o2 dot pl
2009-03-02 22:43 ` pinskia at gcc dot gnu dot org
2009-03-03 0:20 ` galtgendo at o2 dot pl
2009-03-03 0:21 ` pinskia at gcc dot gnu dot org
2009-03-03 3:23 ` galtgendo at o2 dot pl
2009-03-03 3:43 ` galtgendo at o2 dot pl
2009-03-03 3:51 ` pinskia at gcc dot gnu dot org
2009-03-03 15:15 ` galtgendo at o2 dot pl [this message]
2009-03-03 16:17 ` galtgendo at o2 dot pl
2009-03-03 16:22 ` galtgendo at o2 dot pl
2009-03-03 17:01 ` hjl dot tools at gmail dot com
2009-03-03 21:13 ` galtgendo at o2 dot pl
2009-03-07 4:30 ` galtgendo at o2 dot pl
2009-03-07 4:35 ` Andrew Thomas Pinski
2009-03-07 4:36 ` pinskia at gmail dot com
2009-03-07 14:06 ` galtgendo at o2 dot pl
2009-03-16 10:24 ` falk at debian dot org
2009-04-22 0:04 ` galtgendo at o2 dot pl
2009-04-22 0:23 ` galtgendo at o2 dot pl
2009-04-22 1:08 ` galtgendo at o2 dot pl
2009-04-22 1:15 ` galtgendo at o2 dot pl
[not found] <bug-39333-4@http.gcc.gnu.org/bugzilla/>
2011-03-26 8:19 ` dirtyepic at gentoo dot org
2011-03-26 8:25 ` dirtyepic at gentoo dot org
2011-06-29 13:28 ` dexuan.cui at intel dot com
2011-09-11 9:16 ` galtgendo at o2 dot pl
2011-09-11 15:08 ` galtgendo at o2 dot pl
2012-06-17 13:18 ` galtgendo at o2 dot pl
2013-01-06 2:20 ` galtgendo at o2 dot pl
2013-01-06 3:34 ` galtgendo at o2 dot pl
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=20090303151502.30323.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: 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).