From: Jan Hubicka <hubicka@ucw.cz>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Jan Hubicka <jh@suse.cz>, Michael Matz <matz@suse.de>,
Andi Kleen <ak@suse.de>,
gcc-patches@gcc.gnu.org
Subject: Re: "+m" constraints bogus?
Date: Wed, 25 Jul 2007 09:22:00 -0000 [thread overview]
Message-ID: <20070725065444.GA27434@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <de8d50360707241144w7b823be4xbbf8ce2e651c6b0c@mail.gmail.com>
> On 7/24/07, Jan Hubicka <jh@suse.cz> wrote:
> >I will try to find the original Jason's problem, does anyone recall?
>
> well the gimplifier no longer allows "+m" to pass to expand, we always
> expoand the constraints.
Yep, I noticed we decompose it now, however it still does not quite
answer whether we can accept +m now or not... (ie whether there exists
testcases where reload desynchronize input and output constraint for
some good reason).
Honza
next prev parent reply other threads:[~2007-07-25 6:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707231815.49723.ak@suse.de>
2007-07-23 17:37 ` Jan Hubicka
2007-07-24 16:51 ` Michael Matz
2007-07-24 18:18 ` Jan Hubicka
2007-07-24 18:53 ` Andrew Pinski
2007-07-25 9:22 ` Jan Hubicka [this message]
2007-07-25 13:23 ` Michael Matz
2007-07-25 15:59 ` Jan Hubicka
2007-07-25 16:02 ` Michael Matz
2007-07-25 16:10 ` Jan Hubicka
2007-07-25 16:11 ` Michael Matz
2007-07-25 18:45 ` Jan Hubicka
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=20070725065444.GA27434@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=ak@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=matz@suse.de \
--cc=pinskia@gmail.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).