public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/39251] FAIL: g++.dg/tree-ssa/new1.C scan-tree-dump-not forwprop1 "= .* \+ -" Date: Fri, 15 Jan 2010 03:26:00 -0000 [thread overview] Message-ID: <20100115032629.21256.qmail@sourceware.org> (raw) In-Reply-To: <bug-39251-276@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from mmitchel at gcc dot gnu dot org 2010-01-15 03:26 ------- Ramana -- If I'm reading the log correctly for PR36633 the change that Jason made there didn't actually fix the bug; it was just a cleanup. He commented that something else had changed which made the bug go away. However, if this is behaving different on ARM from (say) x86, I think that the ABI is a likely cause because, as you say, the C++ ABI for these bits is subtly different. Do we know that this is ARM-specific? Thanks, -- Mark -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39251
next prev parent reply other threads:[~2010-01-15 3:26 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-19 18:22 [Bug tree-optimization/39251] New: " danglin at gcc dot gnu dot org 2009-02-19 18:28 ` [Bug tree-optimization/39251] " dave at hiauly1 dot hia dot nrc dot ca 2009-05-13 10:10 ` ramana at gcc dot gnu dot org 2009-05-13 13:35 ` rguenth at gcc dot gnu dot org 2009-05-13 15:20 ` dave at hiauly1 dot hia dot nrc dot ca 2010-01-15 1:09 ` ramana at gcc dot gnu dot org 2010-01-15 1:16 ` ramana at gcc dot gnu dot org 2010-01-15 3:26 ` mmitchel at gcc dot gnu dot org [this message] 2010-01-15 9:05 ` ramana at gcc dot gnu dot org 2010-01-15 15:05 ` mark at codesourcery dot com [not found] <bug-39251-4@http.gcc.gnu.org/bugzilla/> 2012-09-23 22:21 ` pinskia at gcc dot gnu.org 2012-09-23 22:40 ` dave.anglin at bell dot net 2021-12-12 9:32 ` 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=20100115032629.21256.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).