public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49886] New: pass_split_functions cannot deal with function type attributes
Date: Thu, 28 Jul 2011 11:42:00 -0000 [thread overview]
Message-ID: <bug-49886-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49886
Summary: pass_split_functions cannot deal with function type
attributes
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jamborm@gcc.gnu.org
CC: hubicka@gcc.gnu.org
Host: i686-linux-gnu, x86_64-linux-gnu
Target: i686-linux-gnu, x86_64-linux-gnu
Build: i686-linux-gnu, x86_64-linux-gnu
Created attachment 24855
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24855
Testcase
pass_split_functions is happy to split functions which have type
attributes but cannot update them if the new clone has in any way
different parameters than the original.
This can lead to miscompilations, for example, the attached testcase
segfaults when compiled at -O3 (on i686 and x86_64 but probably just
everywhere, tested on trunk and a checkout of the 4.6 branch from
July 11). -fno-partial-inlining makes the problem go away.
next reply other threads:[~2011-07-28 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 11:42 jamborm at gcc dot gnu.org [this message]
2011-07-28 11:51 ` [Bug middle-end/49886] [4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-07-28 16:53 ` jamborm at gcc dot gnu.org
2011-08-01 14:53 ` rguenth at gcc dot gnu.org
2011-08-31 17:48 ` jamborm at gcc dot gnu.org
2011-09-02 12:46 ` jamborm at gcc dot gnu.org
2011-09-02 14:31 ` jamborm at gcc dot gnu.org
2011-09-03 19:41 ` jamborm at gcc dot gnu.org
2011-09-06 15:09 ` jamborm at gcc dot gnu.org
2011-09-07 12:02 ` jamborm at gcc dot gnu.org
2011-09-19 6:20 ` terry.guo at arm dot com
2011-09-19 11:46 ` jamborm at gcc dot gnu.org
2011-09-19 13:37 ` jamborm at gcc dot gnu.org
2011-09-19 13:57 ` jamborm 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=bug-49886-4@http.gcc.gnu.org/bugzilla/ \
--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).