public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64113] Gcc on Alpha: Error: No lda !gpdisp!282 was found Date: Mon, 01 Dec 2014 19:49:00 -0000 [thread overview] Message-ID: <bug-64113-4-ynCwO4tUl7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64113-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64113 Uroš Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2014-12-01 Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com Target Milestone|--- |4.9.3 Ever confirmed|0 |1 --- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> --- This is actually a target problem, the quoted patch just exposed it. The problem is in the way call to __tls_get_addr is split. Currently, when the gp register is not used, life analysis removes only UNSPEC_LDGP2 - the last part of the sequence. This call has to be split with a peephole2, in the same way other calls are handled. alpha.md has the comment that says: ;; We must use peep2 instead of a split because we need accurate life ;; information for $gp. Consider the case of { bar(); while (1); }. I have the patch in testing. >From gcc-bugs-return-469135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 01 19:56:42 2014 Return-Path: <gcc-bugs-return-469135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 15664 invoked by alias); 1 Dec 2014 19:56:42 -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 15638 invoked by uid 48); 1 Dec 2014 19:56:38 -0000 From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64113] Gcc on Alpha: Error: No lda !gpdisp!282 was found Date: Mon, 01 Dec 2014 19:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: 4.9.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: <bug-64113-4-85rT48UZLu@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64113-4@http.gcc.gnu.org/bugzilla/> References: <bug-64113-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg00142.txt.bz2 Content-length: 367 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64113 --- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> --- Created attachment 34157 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34157&action=edit Proposed patch Patch in testing. Using this patch, I was able to compile systemd-217 that otherwise failed to compile with the reported error. >From gcc-bugs-return-469136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 01 20:10:09 2014 Return-Path: <gcc-bugs-return-469136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22436 invoked by alias); 1 Dec 2014 20:10:09 -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 22402 invoked by uid 48); 1 Dec 2014 20:10:05 -0000 From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/64144] std::async can deadlock during thread exit Date: Mon, 01 Dec 2014 20:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-64144-4-lUfm3mplbH@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64144-4@http.gcc.gnu.org/bugzilla/> References: <bug-64144-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-12/txt/msg00143.txt.bz2 Content-length: 592 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd144 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- But that one doesn't block because wait_for() returns future_status::ready immediately ... it was failing due to some local changes I had. So I think this is a false alarm.
next prev parent reply other threads:[~2014-12-01 19:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-29 7:30 [Bug target/64113] New: " mcree at orcon dot net.nz 2014-12-01 19:49 ` ubizjak at gmail dot com [this message] 2014-12-02 10:04 ` [Bug target/64113] " uros at gcc dot gnu.org 2014-12-02 19:30 ` uros at gcc dot gnu.org 2014-12-02 19:32 ` ubizjak at gmail dot com 2015-02-22 16:22 ` uros 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-64113-4-ynCwO4tUl7@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: linkBe 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).