public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56301] New: [4.7 Regression] wrong code with the fix for PR53844
Date: Tue, 12 Feb 2013 23:56:00 -0000	[thread overview]
Message-ID: <bug-56301-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56301
           Summary: [4.7 Regression] wrong code with the fix for PR53844
    Classification: Unclassified
           Product: gcc
           Version: 4.7.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: doko@gcc.gnu.org


works with 4.6 branch, 4.7.2 and the trunk. introduced in r195708 by the fix
for PR53844.

I don't have a reduced testcase yet. the unreduced test case is that the
upstart build in Ubuntu raring hangs in the testsuite with:

  Testing job_deserialise() ptrace handling
  BAD: wrong value for job->goal, expected 1 got 0
   at tests/test_job.c:7331 (deserialise_ptrace_next).

still trying to isolate the failure.

afaics, it is not architecture specific.

Even if backports are tested together, it would help if independent patches
could be committed separately to the branches.


             reply	other threads:[~2013-02-12 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 23:56 doko at gcc dot gnu.org [this message]
2013-02-13 11:08 ` [Bug middle-end/56301] " rguenth at gcc dot gnu.org
2013-02-18 12:32 ` doko at gcc dot gnu.org
2013-02-18 12:38 ` doko at gcc dot gnu.org
2013-02-18 12:48 ` rguenth at gcc dot gnu.org
2013-02-18 12:49 ` rguenth at gcc dot gnu.org
2013-02-18 13:31 ` jakub at gcc dot gnu.org
2013-02-18 13:34 ` rguenther at suse dot de
2013-02-18 13:42 ` jakub at gcc dot gnu.org
2013-02-19 13:18 ` doko 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-56301-4@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).