public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [trunk<-vta] Re: [vtab] Permit coalescing of user variables
Date: Sun, 05 Jun 2011 21:07:00 -0000	[thread overview]
Message-ID: <or1uz8f0w1.fsf@livre.localdomain> (raw)
In-Reply-To: <20110604130203.GL17079@tyan-ft48-01.lab.bos.redhat.com> (Jakub	Jelinek's message of "Sat, 4 Jun 2011 15:02:03 +0200")

On Jun  4, 2011, Jakub Jelinek <jakub@redhat.com> wrote:

> The following changes all look wrong to me, they make the tests totally
> useless.  If both f and g are used in real code after the asm volatile, then
> the both f and g will likely live in some register or memory.
> The whole point of the construct in the tests is that f has at that spot
> a reg or mem location, but g isn't present anywhere anymore (as the compiler
> doesn't or shouldn't know that asm volatile hasn't changed f), thus it
> should represent them as bswap/clz/ctz/rotate.

I see.  I'll try to figure out why that didn't work.  Maybe the input
operands were clobbered or something, or maybe g used to be saved
elsewhere before and now it no longer is.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

  reply	other threads:[~2011-06-05 21:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 19:05 Alexandre Oliva
2007-10-02  9:15 ` Richard Guenther
2007-10-02 21:02 ` Andrew MacLeod
2007-10-03  1:11   ` Alexandre Oliva
2007-10-09 21:32     ` Alexandre Oliva
2009-06-01  7:39       ` [trunk<-vta] " Alexandre Oliva
2009-06-01  7:44         ` Alexandre Oliva
2009-06-01 16:11         ` Ian Lance Taylor
2009-06-01 17:35           ` Andrew MacLeod
2009-06-01 19:23             ` Alexandre Oliva
2009-06-02  9:54               ` Richard Guenther
2009-06-02 21:42                 ` Alexandre Oliva
2009-06-03  1:13                   ` Andrew MacLeod
2009-06-03 10:18                     ` Richard Guenther
2009-06-03 17:43                       ` Alexandre Oliva
2009-06-03 18:06                         ` Daniel Jacobowitz
2009-06-03 19:17                           ` Alexandre Oliva
2009-06-03 19:45                             ` Daniel Jacobowitz
2009-06-03 21:42                               ` Alexandre Oliva
2009-06-03 18:18                         ` Richard Guenther
2009-06-03 19:15                           ` Alexandre Oliva
2009-06-03 19:50                             ` Richard Guenther
2009-06-03 19:53                               ` Ian Lance Taylor
2009-10-13 21:27         ` Alexandre Oliva
2011-06-04 12:45           ` Alexandre Oliva
2011-06-04 13:02             ` Jakub Jelinek
2011-06-05 21:07               ` Alexandre Oliva [this message]
2011-06-06  2:42                 ` Alexandre Oliva
2012-04-09  5:56             ` Alexandre Oliva
2012-06-13  8:34               ` Alexandre Oliva
2012-06-13  9:48                 ` Richard Guenther

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=or1uz8f0w1.fsf@livre.localdomain \
    --to=aoliva@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).