public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: "gcc-bugzilla@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug optimization/13379] 3.5-tree-ssa 20031210 miscompiles 2.6.0-test11 Linux kernel
Date: Wed, 10 Dec 2003 20:31:00 -0000	[thread overview]
Message-ID: <1071088242.8617.94.camel@frodo.toronto.redhat.com> (raw)
In-Reply-To: <20031210202600.32390.qmail@sources.redhat.com>

On Wed, 2003-12-10 at 15:26, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2003-12-10 20:25 -------
> dberlin said this should be in waiting as the problem is most likely an aliasing problem in the code.
>
Not quite.  The chat on IRC was more along the lines of "I can't see
anything obviously wrong with what's coming out of PRE".  But IRC is
notoriously noisy.


Diego.


  reply	other threads:[~2003-12-10 20:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 20:00 [Bug c/13379] New: " mingo at elte dot hu
2003-12-10 20:02 ` [Bug c/13379] " mingo at elte dot hu
2003-12-10 20:25 ` pinskia at gcc dot gnu dot org
2003-12-10 20:26 ` [Bug optimization/13379] " pinskia at gcc dot gnu dot org
2003-12-10 20:31   ` Diego Novillo [this message]
2003-12-10 20:31 ` rth at gcc dot gnu dot org
2003-12-10 20:31 ` dnovillo at redhat dot com
2003-12-10 21:22 ` mingo at elte dot hu
2003-12-10 21:33 ` dnovillo at gcc dot gnu dot org
2003-12-10 23:03 ` dnovillo at gcc dot gnu dot org
2003-12-11  1:19 ` dberlin at gcc dot gnu dot org
2003-12-11 18:34 ` mingo at elte dot hu
2003-12-11 18:39 ` dnovillo at redhat dot com
2003-12-12 12:36 ` mingo at elte dot hu
2004-01-30 11:30 ` [Bug optimization/13379] [tree-ssa] " steven at gcc dot gnu dot org
2004-01-30 15:05 ` mingo at elte dot hu
2004-01-30 15:19 ` mingo at elte dot hu
2004-02-03  1:52 ` rth at gcc dot gnu dot org
2004-02-03  3:15 ` rth at gcc dot gnu dot org
2004-02-03  9:10 ` mingo at elte dot hu
2004-02-03  9:11 ` mingo at elte dot hu
2004-02-29 13:38 ` steven at gcc dot gnu dot org
2004-03-01  7:22 ` mingo at elte dot hu
2004-03-01  7:34 ` mingo at elte dot hu
2004-03-01  7:37 ` mingo at elte dot hu
2004-03-01  7:58 ` pinskia at gcc dot gnu dot org
2004-03-01 18:23 ` dnovillo at gcc dot gnu dot org
2004-03-01 18:25 ` dnovillo at redhat dot com
2004-03-01 18:31 ` steven at gcc dot gnu dot org
2004-03-02  1:12 ` mingo at elte dot hu
2004-03-02  2:20 ` dnovillo at redhat dot com

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=1071088242.8617.94.camel@frodo.toronto.redhat.com \
    --to=dnovillo@redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).