public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oakad at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37107] Incorrect code generated after function inlining
Date: Wed, 20 Aug 2008 06:34:00 -0000 [thread overview]
Message-ID: <20080820063254.31178.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37107-7690@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from oakad at yahoo dot com 2008-08-20 06:32 -------
(In reply to comment #3)
> Can you provide the preprocessed source which you can get via the -save-temps
> option. Also does using -fno-strict-aliasing fix the issue?
>
-fno-strict-aliasing appears to have no effect on issue.
Different optimization level (-O2) still generates problematic code.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37107
next prev parent reply other threads:[~2008-08-20 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 8:10 [Bug c/37107] New: " oakad at yahoo dot com
2008-08-13 8:11 ` [Bug c/37107] " oakad at yahoo dot com
2008-08-13 8:12 ` oakad at yahoo dot com
2008-08-16 22:15 ` [Bug middle-end/37107] " pinskia at gcc dot gnu dot org
2008-08-20 6:34 ` oakad at yahoo dot com [this message]
2008-08-20 6:35 ` oakad at yahoo dot com
2008-08-20 6:35 ` oakad at yahoo dot com
2008-12-27 6:23 ` pinskia at gcc dot gnu dot org
[not found] <bug-37107-4@http.gcc.gnu.org/bugzilla/>
2012-01-13 6:41 ` pinskia at gcc dot gnu.org
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=20080820063254.31178.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).