public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60770] disappearing clobbers
Date: Sat, 28 Jun 2014 07:26:00 -0000	[thread overview]
Message-ID: <bug-60770-4-ZBW5y2deYA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60770-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60770

--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
Created attachment 33024
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33024&action=edit
replace clobber with default def

This passes bootstrap+testsuite with all default languages, but it breaks ada,
I get plenty of warnings (as if it was reading objects after clobbering them)
and 2 errors about "Unable to coalesce ssa_names [...] which are marked as MUST
COALESCE."

I am probably doing something wrong in the patch, but ada seems to be using
clobbers differently than others since it is the only one that notices (well, I
didn't have a chance to check go since ada broke early).

It would also be nice to save the info somewhere that this default def actually
comes from a clobber, so the uninit pass can give a different warning message.
Maybe there is a bit available in the gimple_nop...


  parent reply	other threads:[~2014-06-28  7:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05 22:31 [Bug tree-optimization/60770] New: " glisse at gcc dot gnu.org
2014-04-06  8:55 ` [Bug tree-optimization/60770] " manu at gcc dot gnu.org
2014-04-07 10:18 ` rguenth at gcc dot gnu.org
2014-04-07 11:31 ` glisse at gcc dot gnu.org
2014-06-22 21:07 ` glisse at gcc dot gnu.org
2014-06-27  6:53 ` glisse at gcc dot gnu.org
2014-06-28  7:26 ` glisse at gcc dot gnu.org [this message]
2014-06-28 11:10 ` ebotcazou at gcc dot gnu.org
2014-06-28 12:27 ` glisse at gcc dot gnu.org
2014-11-03 10:47 ` glisse at gcc dot gnu.org
2014-11-22 14:28 ` glisse at gcc dot gnu.org
2021-01-27 17:02 ` orgads at gmail dot com
2021-01-27 17:10 ` glisse at gcc dot gnu.org
2021-01-27 18:48 ` orgads at gmail dot com

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-60770-4-ZBW5y2deYA@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).