public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "torvald at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/51771] New: trans-mem: abnormal edges get lost or corrupted Date: Thu, 05 Jan 2012 23:44:00 -0000 [thread overview] Message-ID: <bug-51771-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51771 Bug #: 51771 Summary: trans-mem: abnormal edges get lost or corrupted Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: torvald@gcc.gnu.org CC: aldyh@gcc.gnu.org, rth@gcc.gnu.org For each call to libitm we create an abnormal edge back to the transaction's begin, which models that libitm could restart. Those edges seem to be intact during the middle-end but get lost or corrupted somewhere after that. This leads to miscompilation of STAMP Genome on x86_64, for example. For 4.7, we can mark _ITM_beginTransaction as returns-twice. This seems to work but isn't optimal, so we should fix the handling of abnormal edges for 4.8.
next reply other threads:[~2012-01-05 23:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-05 23:44 torvald at gcc dot gnu.org [this message] 2012-01-05 23:49 ` [Bug rtl-optimization/51771] " torvald at gcc dot gnu.org 2012-01-17 23:58 ` patrick.marlier at gmail dot com 2012-01-31 13:35 ` torvald at gcc dot gnu.org 2012-01-31 13:56 ` torvald at gcc dot gnu.org 2012-05-03 15:07 ` luked at cs dot rochester.edu 2012-06-01 16:40 ` aldyh at gcc dot gnu.org 2012-06-01 16:47 ` aldyh at gcc dot gnu.org 2012-06-01 16:53 ` aldyh at gcc dot gnu.org 2012-06-04 16:09 ` aldyh at gcc dot gnu.org 2012-11-29 17:05 ` aldyh at gcc dot gnu.org 2012-12-03 18:43 ` aldyh at gcc dot gnu.org 2012-12-03 18:52 ` aldyh at gcc dot gnu.org 2012-12-05 19:19 ` torvald 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-51771-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: 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).