public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Thomas Pinski <pinskia@gmail.com>
To: "gcc-bugzilla@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Subject: Re: [Bug middle-end/39015] [4.3 regression] wrong code building libgsf
Date: Thu, 29 Jan 2009 17:53:00 -0000	[thread overview]
Message-ID: <FE28424C-76F6-4B3A-8F27-78769C1A4428@gmail.com> (raw)
In-Reply-To: <20090129100101.32636.qmail@sourceware.org>



Sent from my iPhone

On Jan 29, 2009, at 2:01 AM, "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org 
 > wrote:

>
>
> ------- Comment #3 from rguenth at gcc dot gnu dot org  2009-01-29  
> 10:01 -------
> The best option would be to revert that patch on the branch.

Except it alone could not cause wrong code.  Some other pass is  
causing it.  And then again with a testcase it is hard to figure out  
what is going wrong.  That patch just disables one small optimization  
in one case.

>
>
>
> -- 
>
> rguenth at gcc dot gnu dot org changed:
>
>           What    |Removed                     |Added
> --- 
> --- 
> ----------------------------------------------------------------------
>                 CC|                            |sje at gcc dot gnu  
> dot org,
>                   |                            |rguenth at gcc dot  
> gnu dot
>                   |                            |org
>           Priority|P3                          |P1
>   Target Milestone|---                         |4.3.4
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39015
>


  reply	other threads:[~2009-01-29 17:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  5:39 [Bug middle-end/39015] New: " doko at ubuntu dot com
2009-01-29  9:10 ` [Bug middle-end/39015] " jdassen at debian dot org
2009-01-29  9:11 ` jdassen at debian dot org
2009-01-29 10:01 ` rguenth at gcc dot gnu dot org
2009-01-29 17:53   ` Andrew Thomas Pinski [this message]
2009-01-29 10:14 ` doko at ubuntu dot com
2009-01-29 10:24 ` jdassen at debian dot org
2009-01-29 17:01 ` sje at cup dot hp dot com
2009-01-29 17:53 ` pinskia at gmail dot com
2009-01-29 17:53 ` jdassen at debian dot org
2009-01-29 18:57 ` sje at cup dot hp dot com
2009-01-29 22:36 ` [Bug middle-end/39015] [4.3/4.4 " doko at ubuntu dot com
2009-01-29 22:40 ` pinskia at gcc dot gnu dot org
2009-01-29 22:42 ` pinskia at gcc dot gnu dot org
2009-01-30 10:58 ` jakub at gcc dot gnu dot org
2009-01-30 11:38 ` jakub at gcc dot gnu dot org
2009-01-30 11:39 ` jakub at gcc dot gnu dot org
2009-01-30 11:40 ` jakub at gcc dot gnu dot org
2009-01-30 17:03 ` jdassen at debian dot org

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=FE28424C-76F6-4B3A-8F27-78769C1A4428@gmail.com \
    --to=pinskia@gmail.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).