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/52146] [x32] - Wrong code to access addresses 0x80000000 to 0xFFFFFFFF Date: Thu, 09 Feb 2012 22:35:00 -0000 [thread overview] Message-ID: <bug-52146-4-bYRFCLrL5I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52146-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52146 Uros Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hjl.tools at gmail dot com --- Comment #4 from Uros Bizjak <ubizjak at gmail dot com> 2012-02-09 22:35:05 UTC --- CC author.
next prev parent reply other threads:[~2012-02-09 22:35 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-07 8:55 [Bug c/52146] New: " steffen-schmidt at siemens dot com 2012-02-07 8:58 ` [Bug c/52146] " steffen-schmidt at siemens dot com 2012-02-07 8:58 ` steffen-schmidt at siemens dot com 2012-02-07 17:07 ` [Bug target/52146] " pinskia at gcc dot gnu.org 2012-02-09 22:35 ` ubizjak at gmail dot com [this message] 2012-02-10 0:21 ` hjl.tools at gmail dot com 2012-02-10 7:44 ` jakub at gcc dot gnu.org 2012-02-10 10:15 ` ubizjak at gmail dot com 2012-02-10 12:23 ` steffen-schmidt at siemens dot com 2012-02-10 17:06 ` ubizjak at gmail dot com 2012-02-10 17:29 ` hjl.tools at gmail dot com 2012-02-10 17:43 ` ubizjak at gmail dot com 2012-02-10 17:49 ` jakub at gcc dot gnu.org 2012-02-10 18:02 ` ubizjak at gmail dot com 2012-02-10 18:23 ` hjl at gcc dot gnu.org 2012-02-10 20:03 ` hjl at gcc dot gnu.org 2012-02-11 4:21 ` hjl.tools at gmail dot com 2012-02-11 4:23 ` hjl.tools at gmail dot com 2012-02-13 10:52 ` steffen-schmidt at siemens dot com 2012-02-23 17:29 ` pinskia at gcc dot gnu.org 2012-03-04 21:18 ` hjl 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-52146-4-bYRFCLrL5I@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).