public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xinliang David Li <davidxl@google.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [lipo] merge from trunk
Date: Wed, 22 Jul 2009 08:28:00 -0000	[thread overview]
Message-ID: <522e93240907212321m221647ccu32d3f7c03b25e82c@mail.gmail.com> (raw)

Merged revisions 149500-149501,149503,149506-149509,149511,149513-149516,
149518-149520,149523-149526,149530,149532-149537,149540,149544-149553,
149556-149586,149590-149591,149593-149594,149603,149611-149612,149614,
149624,149626-149629,149631-149632,149635-149639,149641,149644,149647-149650,
149653,149655,149661-149680,149685-149686,149688-149691,149694,149696,
149700-149702,149704-149705,149712,149714-149716,149719,149721-149722,
149725,149730-149731,149733-149734,149736-149737,149740,149744,149746,
149748,149750,149755-149757,149762-149763,149765-149766,149770,149772,
149774,149778-149782,149785,149789,149792-149794,149797,149800,149803,
149805-149813,149816-149817,149819-149822,149825-149827,149829-149836

Tested: SPEC2k, SPEC06 with LIPO.

David

             reply	other threads:[~2009-07-22  6:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22  8:28 Xinliang David Li [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-07 21:51 Raksit Ashok
2010-09-06  8:58 Raksit Ashok
2010-08-19 13:29 Raksit Ashok
2010-08-10 10:13 Raksit Ashok
2010-08-05  9:59 Raksit Ashok
2010-06-10 12:01 Raksit Ashok
2010-06-09 17:47 Raksit Ashok
2010-06-09  8:44 Raksit Ashok
2010-06-08 10:52 Raksit Ashok
2010-06-07 12:24 Raksit Ashok
2010-06-07  7:40 Raksit Ashok
2010-06-03  7:48 Raksit Ashok
2010-06-02  7:40 Raksit Ashok
2010-05-04 11:21 Raksit Ashok
2009-11-05  5:19 Xinliang David Li
2009-09-30 18:53 [lipo]: " Xinliang David Li
2009-08-06 16:58 [lipo] " Xinliang David Li
2009-07-14  0:32 Xinliang David Li
2009-06-26  3:46 Xinliang David Li
2009-06-01  5:59 [lipo]: " Xinliang David Li

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=522e93240907212321m221647ccu32d3f7c03b25e82c@mail.gmail.com \
    --to=davidxl@google.com \
    --cc=gcc-patches@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).