From: "Andrew Pinski" <pinskia@gmail.com>
To: "Zdenek Dvorak" <rakdver@kam.mff.cuni.cz>
Cc: Andrew_Pinski@playstation.sony.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix IV-opts so it no longer produces MEM[index:]
Date: Fri, 10 Aug 2007 21:21:00 -0000 [thread overview]
Message-ID: <de8d50360708101420x45d85a60j8eb745c3cc6df810@mail.gmail.com> (raw)
In-Reply-To: <20070801095236.GA13479@kam.mff.cuni.cz>
On 8/1/07, Zdenek Dvorak <rakdver@kam.mff.cuni.cz> wrote:
> These changes look wrong; for example, if aff_combination_to_tree is
> called with combination with elements i and p (where type of p = int *
> and type of i is sizetype), this would end up producing
> (int *) i PPLUS (sizetype) p.
Even if we produce that, fold_binary will convert it to be p PPLUS i
anyways. So this might be ok, I have to double check (maybe this is
no longer needed).
Thanks,
Andrew Pinski
prev parent reply other threads:[~2007-08-10 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 2:36 Andrew_Pinski
2007-08-01 9:52 ` Zdenek Dvorak
2007-08-01 21:18 ` Andrew_Pinski
2007-08-07 12:26 ` Andrew Pinski
2007-08-08 10:18 ` Zdenek Dvorak
2007-08-10 21:21 ` Andrew Pinski [this message]
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=de8d50360708101420x45d85a60j8eb745c3cc6df810@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=Andrew_Pinski@playstation.sony.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rakdver@kam.mff.cuni.cz \
/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).