public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ondrej at sury dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/57080] Invalid optimization (-O2) when doing double -> int conversion (on big endian archs(?))
Date: Fri, 26 Apr 2013 10:27:00 -0000	[thread overview]
Message-ID: <bug-57080-4-UCnP9yA3y8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57080-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57080

--- Comment #1 from Ondřej Surý <ondrej at sury dot org> 2013-04-26 10:27:30 UTC ---
Created attachment 29945
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29945
Generated from gd.c, affected code is in clip_1d function
>From gcc-bugs-return-421009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 10:37:59 2013
Return-Path: <gcc-bugs-return-421009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5516 invoked by alias); 26 Apr 2013 10:37:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5495 invoked by uid 48); 26 Apr 2013 10:37:56 -0000
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55708] g++ crashes: constexpr function with reference parameters.
Date: Fri, 26 Apr 2013 10:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: daniel.kruegler at googlemail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55708-4-EPbq0WTud8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55708-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55708-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-SW-Source: 2013-04/txt/msg02154.txt.bz2
Content-length: 246


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55708

--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2013-04-26 10:37:55 UTC ---
gcc 4.9.0 20130421 (experimental) accepts the code on my system (64-bit mingw).
>From gcc-bugs-return-421010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 10:54:48 2013
Return-Path: <gcc-bugs-return-421010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21609 invoked by alias); 26 Apr 2013 10:54:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21566 invoked by uid 48); 26 Apr 2013 10:54:45 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57075] [4.9 Regression] verify_flow_info failed: control flow in the middle of basic block
Date: Fri, 26 Apr 2013 10:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Changed-Fields:
Message-ID: <bug-57075-4-85pimWrgfN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57075-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57075-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-SW-Source: 2013-04/txt/msg02155.txt.bz2
Content-length: 466


http://gcc.gnu.org/bugzilla/show_bug.cgi?idW075

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> 2013-04-26 10:54:45 UTC ---
Ok, I think I reduced this issue to this:

/* PR tree-optimization/57075 */
/* { dg-do compile } */
/* { dg-options "-O2" } */

extern int baz (void) __attribute__ ((returns_twice));
int __attribute__ ((__leaf__))
foo (void)
{
  return __builtin_printf ("$");
}

void
bar ()
{
  foo ();
  baz ();
}


  reply	other threads:[~2013-04-26 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 10:26 [Bug c/57080] New: " ondrej at sury dot org
2013-04-26 10:27 ` ondrej at sury dot org [this message]
2013-04-26 11:04 ` [Bug c/57080] " ondrej at sury dot org
2013-04-26 12:32 ` ondrej at sury dot org
2013-04-26 16:11 ` pinskia at gcc dot gnu.org
2013-04-26 17:15 ` jakub at gcc dot gnu.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=bug-57080-4-UCnP9yA3y8@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).