public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Paolo Carlini <pcarlini@unitus.it>
Cc: Richard Henderson <rth@redhat.com>, gcc@gcc.gnu.org
Subject: Re: Loop unrolling-related SPEC regressions?
Date: Mon, 04 Feb 2002 08:37:00 -0000	[thread overview]
Message-ID: <u8d6zlryta.fsf@gromit.moeb> (raw)
In-Reply-To: <3C5AE860.2AA390F1@unitus.it>

Paolo Carlini <pcarlini@unitus.it> writes:

> Perhaps we could ask Andreas to help by running an exceptional SPEC test with
> -funroll-loops instead (ideally, 2 different runs, pre- and post- the unroller
> patch).

Sorry for joining in late, I've been travelling.

Tell me exactly which patch I should revert and which compiler flags I
should use and I'll bootstrap two GCCs and run one SPECint run using
the different compilers for base and peak.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2002-02-04 16:37 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 10:32 Paolo Carlini
2002-02-01 10:46 ` Richard Henderson
2002-02-01 10:51   ` Paolo Carlini
2002-02-01 10:57     ` Richard Henderson
2002-02-01 11:12       ` Paolo Carlini
2002-02-04  8:37         ` Andreas Jaeger [this message]
2002-02-04  9:05           ` Paolo Carlini
2002-02-04 11:15             ` Andreas Jaeger
2002-02-06  0:59             ` Andreas Jaeger
2002-02-06  1:05               ` Paolo Carlini
2002-02-06  1:39                 ` Andreas Jaeger
2002-02-06  1:43                   ` Paolo Carlini
2002-02-06  1:43                     ` Andreas Jaeger
2002-02-06  1:50                     ` Andreas Jaeger
2002-02-06 13:08               ` Andreas Jaeger
2002-02-06 14:09                 ` Laurent Guerby
2002-02-06 14:45                   ` Dale Johannesen
2002-02-06 15:08                     ` Andreas Jaeger
2002-02-07  3:59                       ` Jan Hubicka
2002-02-07  7:27                       ` Michael Matz
2002-02-07  3:48                     ` Jan Hubicka
2002-02-07  9:42                       ` Richard Henderson
2002-02-06 15:00                   ` Andreas Jaeger
2002-02-07  5:22                     ` Laurent Guerby
2002-02-07  5:46                       ` Cannot allocate 92625564 bytes after allocating 198356992 bytes Dimitri Frederickx
     [not found]                       ` <ho8za5ijlt.fsf@gee.suse.de>
2002-02-07 11:52                         ` Loop unrolling-related SPEC regressions? Laurent Guerby
2002-02-01 11:14 ` Joe Buck
2002-02-04  8:45   ` Andreas Jaeger
2002-02-04 10:58   ` Jan Hubicka
2002-02-04 11:07     ` Paolo Carlini
2002-02-04 12:12       ` Andreas Jaeger
2002-02-04 16:36         ` Paolo Carlini
2002-02-04 21:34         ` Tim Prince
2002-02-05  4:32           ` Jan Hubicka
2002-02-05 14:05             ` Geoff Keating
2002-02-06  3:32               ` Jan Hubicka
2002-02-05 20:57             ` Tim Prince
2002-02-04 11:20     ` Joe Buck
2002-02-04 11:33       ` Jan Hubicka
2002-02-04 11:47         ` Jan Hubicka
2002-02-05  9:59         ` David Edelsohn

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=u8d6zlryta.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=pcarlini@unitus.it \
    --cc=rth@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).