public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Serious problems with tree-ssa operand handling
Date: Wed, 15 Sep 2004 18:39:00 -0000	[thread overview]
Message-ID: <20040915095846.A18047@synopsys.com> (raw)
In-Reply-To: <1094570838.21733.57.camel@localhost.localdomain>; from dnovillo@redhat.com on Tue, Sep 07, 2004 at 11:27:18AM -0400

On Tue, Sep 07, 2004 at 11:27:18AM -0400, Diego Novillo wrote:
> On Tue, 2004-09-07 at 11:27, Richard Kenner wrote:
> 
> >     Do you have a variable that is a GIMPLE reg and at the same time
> >     belongs to an alias set or its address is taken?
> > 
> > Yes.  See my later message.
> >
> What later message?  Thanks to your reluctance to use a properly
> threading mailer, I find it impossible to follow the threads that you
> contribute to.  Lately, I have had to start ignoring threads that you
> break with your MUA, so I don't know what you are talking about.

Agreed; any long thread Kenner participates in is unreadable.

Here's an item for the projects file: let's call it "deKennerize".  Given
an mbox file full of gcc messages, try to deduce what message each message
from Richard Kenner is replying to, using subjects, dates, recipients, and
quoted text as clues.  Produce a new mbox file with proper References or
In-Reply-To headers added.

This is easiest given a Perl or Python module that supports parsing of
mbox files into messages and headers.


  reply	other threads:[~2004-09-15 16:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 15:24 Richard Kenner
2004-09-07 15:27 ` Diego Novillo
2004-09-15 18:39   ` Joe Buck [this message]
2004-09-15 18:52     ` Gabriel Dos Reis
  -- strict thread matches above, loose matches on Subject: below --
2004-09-17  1:33 Richard Kenner
2004-09-16 14:48 Richard Kenner
2004-09-16 15:16 ` Richard Earnshaw
2004-09-16 23:26 ` Kai Henningsen
2004-09-17  1:27   ` Erik Trulsson
2004-09-16 13:31 Richard Kenner
2004-09-16 11:54 Richard Kenner
2004-09-16 14:30 ` Daniel Berlin
2004-09-16 11:32 Richard Kenner
2004-09-16 12:25 ` Gabriel Dos Reis
2004-09-16 15:39 ` Robert Dewar
2004-09-16  3:11 Richard Kenner
2004-09-16  3:23 ` Gabriel Dos Reis
2004-09-16  5:45 ` Richard Henderson
2004-09-07 20:41 Richard Kenner
2004-09-07 11:45 Richard Kenner
2004-09-07 14:12 ` Diego Novillo

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=20040915095846.A18047@synopsys.com \
    --to=joe.buck@synopsys.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).