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/55145] [4.8 Regression] [x32] -maddress-mode=long miscompiles glibc Date: Thu, 01 Nov 2012 10:09:00 -0000 [thread overview] Message-ID: <bug-55145-4-lFLsPQ294f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55145-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55145 Uros Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2012-11-01 Ever Confirmed|0 |1 --- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2012-11-01 10:08:50 UTC --- So is this PR a manifestation of presumably wrong fix for PR 55142 or an independent bug?
next prev parent reply other threads:[~2012-11-01 10:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-31 5:39 [Bug target/55145] New: " hjl.tools at gmail dot com 2012-10-31 10:27 ` [Bug target/55145] " rguenth at gcc dot gnu.org 2012-11-01 10:09 ` ubizjak at gmail dot com [this message] 2012-11-01 22:29 ` hjl.tools at gmail dot com 2012-11-04 8:11 ` [Bug middle-end/55145] Different bits for long double constant depending ptr_mode hjl.tools at gmail dot com 2012-11-04 10:14 ` [Bug middle-end/55145] Different bits for long double constant depending on long int size hjl.tools at gmail dot com 2012-11-04 11:04 ` schwab@linux-m68k.org 2012-11-04 11:09 ` hjl.tools at gmail dot com 2012-11-04 22:52 ` hjl.tools at gmail dot com 2012-11-04 23:43 ` vincent-gcc at vinc17 dot net 2013-03-22 14:45 ` jakub at gcc dot gnu.org 2013-05-31 10:59 ` jakub at gcc dot gnu.org 2013-10-16 9:49 ` jakub at gcc dot gnu.org 2013-11-20 14:40 ` jsm28 at gcc dot gnu.org 2013-11-20 14:41 ` jsm28 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-55145-4-lFLsPQ294f@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).