public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/50677] volatile forces load into register
Date: Mon, 24 Feb 2014 16:17:00 -0000	[thread overview]
Message-ID: <bug-50677-4-MU0lyvjce5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50677-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50677

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #4)
> Why doesn't combine include (clobber (reg:CC 17 flags))?

It has nothing to do with the clobber.
Inside combine_instructions there is a call to init_recog_no_volatile which
forces volatile memory not be recognized.  The main reason is because combine
does not check for volatile memory issues before doing the combine so it was
easier to just disable recognizability of volatile memory.


  parent reply	other threads:[~2014-02-24 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 12:52 [Bug rtl-optimization/50677] New: " marc.glisse at normalesup dot org
2011-10-09 17:36 ` [Bug rtl-optimization/50677] " rguenth at gcc dot gnu.org
2011-10-09 19:49 ` pinskia at gcc dot gnu.org
2014-02-24 16:03 ` hjl.tools at gmail dot com
2014-02-24 16:17 ` pinskia at gcc dot gnu.org [this message]
2015-07-15 16:37 ` hjl.tools at gmail dot com
2015-07-15 17:07 ` hjl.tools at gmail dot com
2021-11-29  3:17 ` pinskia at gcc dot gnu.org
2022-09-27 23:37 ` pinskia at gcc dot gnu.org
2023-02-09 18:11 ` 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=bug-50677-4-MU0lyvjce5@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).