public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/43879]  New: [4.6 Regression] -fipa-pta causes FAIL: gcc.c-torture/execute/20000822-1.c execution
Date: Sat, 24 Apr 2010 15:54:00 -0000	[thread overview]
Message-ID: <bug-43879-14164@http.gcc.gnu.org/bugzilla/> (raw)

Tested revisions:
r158683 - fail
r158486 - OK

Compiler output:
$ binary-158683-lto-fortran/bin/gcc -O2 -fipa-pta
gcc/testsuite/gcc.c-torture/execute/20000822-1.c && ./a.out
gcc/testsuite/gcc.c-torture/execute/20000822-1.c: In function 'main':
gcc/testsuite/gcc.c-torture/execute/20000822-1.c:25:5: warning: incompatible
implicit declaration of built-in function 'abort' [enabled by default]
Aborted

Is -fipa-pta still no-op?


-- 
           Summary: [4.6 Regression] -fipa-pta causes FAIL: gcc.c-
                    torture/execute/20000822-1.c execution
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: zsojka at seznam dot cz
  GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu


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


             reply	other threads:[~2010-04-24 15:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 15:54 zsojka at seznam dot cz [this message]
2010-04-24 16:18 ` [Bug tree-optimization/43879] " zsojka at seznam dot cz
2010-04-24 18:49 ` [Bug tree-optimization/43879] [4.6 Regression] -fipa-pta causes various miscompilations zsojka at seznam dot cz
2010-04-24 18:55 ` [Bug tree-optimization/43879] " rguenth at gcc dot gnu dot org
2010-04-24 20:04 ` rguenth at gcc dot gnu dot org
2010-04-28 11:52 ` rguenth at gcc dot gnu dot org
2010-04-28 12:53 ` rguenth at gcc dot gnu dot org
2010-04-28 15:09 ` zsojka at seznam dot cz
2010-04-28 15:13 ` zsojka at seznam dot cz
2010-04-29 15:30 ` rguenth at gcc dot gnu dot org
2010-04-29 15:37 ` rguenth at gcc dot gnu dot org
2010-04-30  8:23 ` rguenth at gcc dot gnu dot org
2010-04-30  9:32 ` rguenth at gcc dot gnu dot org
2010-04-30 10:06 ` rguenth at gcc dot gnu dot org
2010-04-30 13:57 ` rguenth at gcc dot gnu dot org
2010-04-30 14:51 ` dominiq at lps dot ens dot fr
2010-04-30 15:17 ` rguenth at gcc dot gnu dot org
2010-04-30 15:27 ` jv244 at cam dot ac dot uk
2010-04-30 15:53 ` dominiq at lps dot ens dot fr
2010-04-30 17:13 ` rguenth at gcc dot gnu dot org
2010-04-30 18:54 ` rguenth at gcc dot gnu dot org
2010-05-02 13:45 ` zsojka at seznam dot cz
2010-05-02 13:47 ` zsojka at seznam dot cz
2010-05-02 18:11 ` rguenth at gcc dot gnu dot org
2010-05-02 18:12 ` rguenth at gcc dot gnu dot org
2010-05-03 14:56 ` zsojka at seznam dot cz
2010-05-03 15:02 ` zsojka at seznam dot cz
2010-05-03 16:56 ` steven at gcc dot gnu dot org
2010-05-03 23:46 ` zsojka at seznam dot cz
2010-05-04 11:16 ` rguenth at gcc dot gnu dot org
2010-05-04 13:13 ` rguenth at gcc dot gnu dot org
2010-05-04 14:02 ` rguenth at gcc dot gnu 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=bug-43879-14164@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).