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/58066] __tls_get_addr is called with misaligned stack on x86-64 Date: Thu, 30 Jul 2015 09:00:00 -0000 [thread overview] Message-ID: <bug-58066-4-vxZxgz7Vgm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58066-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58066 Uroš Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|6.0 |4.9.4 --- Comment #21 from Uroš Bizjak <ubizjak at gmail dot com> --- Fixed everywhere. >From gcc-bugs-return-493737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jul 30 09:01:46 2015 Return-Path: <gcc-bugs-return-493737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 51957 invoked by alias); 30 Jul 2015 09:01:46 -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 51907 invoked by uid 48); 30 Jul 2015 09:01:42 -0000 From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/67002] [5] [SH]: Bootstrap stage 2/3 comparison failure - gcc/real.o differs Date: Thu, 30 Jul 2015 09:01: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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: Message-ID: <bug-67002-4-jXZFaeRVQY@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67002-4@http.gcc.gnu.org/bugzilla/> References: <bug-67002-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: 2015-07/txt/msg02627.txt.bz2 Content-length: 1104 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg002 --- Comment #10 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> --- (In reply to Oleg Endo from comment #9) > Not sure if this is a good idea. I actually think it is the best option as chances are dim otherwise that we find what's actually causing this register indeterminacy. Looking at the build log, it's only gcc/real.o where the comparison fails, all the others (except for the checksum files) are find. I think chances are that, if this is actually a real bug, it might show itself more pronounced when we use gcc-5 to build other packages. Just look at how many bugs we were able to find in gcc-4.9 while using it as the standard host compiler on Debian sh4. You are right that ignoring this failure is most certainly not the best on a release architecture that people rely on. But currently, Debian on sh4 is merely just a port and things are expected to break from time to time. I am currently building now a patched gcc-5_5.2.1-12 which has gcc/real.o added to compare_exclusions, let's see how far we get. Adrian
prev parent reply other threads:[~2015-07-30 9:00 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-02 23:12 [Bug c/58066] New: GCC mis-compiles access to TLS variable with -fPIC on x86_64 ppluzhnikov at google dot com 2013-08-02 23:57 ` [Bug target/58066] " pinskia at gcc dot gnu.org 2013-08-06 23:14 ` ppluzhnikov at google dot com 2014-03-12 21:05 ` hjl.tools at gmail dot com 2014-03-12 22:22 ` hjl.tools at gmail dot com 2014-05-19 5:26 ` wmi at gcc dot gnu.org 2014-12-18 17:54 ` dvyukov at google dot com 2015-07-11 21:03 ` [Bug target/58066] __tls_get_addr is called with misaligned stack on x86-64 hjl.tools at gmail dot com 2015-07-13 3:58 ` hjl.tools at gmail dot com 2015-07-13 6:41 ` ubizjak at gmail dot com 2015-07-13 9:16 ` [Bug rtl-optimization/58066] " ubizjak at gmail dot com 2015-07-13 11:08 ` ubizjak at gmail dot com 2015-07-13 12:08 ` hjl.tools at gmail dot com 2015-07-15 7:40 ` uros at gcc dot gnu.org 2015-07-15 7:41 ` [Bug target/58066] " ubizjak at gmail dot com 2015-07-15 13:42 ` uros at gcc dot gnu.org 2015-07-23 18:52 ` uros at gcc dot gnu.org 2015-07-30 8:54 ` uros at gcc dot gnu.org 2015-07-30 9:00 ` ubizjak at gmail dot com [this message]
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-58066-4-vxZxgz7Vgm@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).