public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libobjc/34315] libobjc warnings with Win64 target=x86_64-pc-mingw32 Date: Sat, 16 Feb 2008 20:47:00 -0000 [thread overview] Message-ID: <20080216204651.26713.qmail@sourceware.org> (raw) In-Reply-To: <bug-34315-14772@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from ktietz at gcc dot gnu dot org 2008-02-16 20:46 ------- Yes, for the x86_64-pc-mingw32 the %ld printing exists, but it is for long, not for long long. For this target long is 32-bit scalar, so the printf formatters are wrong. in gthr-win32.h there seems to be a more serious bug. The cast of an integer with less size to a pointer can be seriously wrong. -- ktietz at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ktietz at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34315
next prev parent reply other threads:[~2008-02-16 20:47 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-02 19:46 [Bug libobjc/34315] New: libobjc warnings with Win64 arget=x86_64-pc-mingw32 nightstrike at gmail dot com 2007-12-02 19:49 ` [Bug libobjc/34315] " nightstrike at gmail dot com 2007-12-12 17:34 ` [Bug libobjc/34315] libobjc warnings with Win64 target=x86_64-pc-mingw32 nightstrike at gmail dot com 2008-02-16 20:47 ` ktietz at gcc dot gnu dot org [this message] 2008-04-21 12:55 ` fxcoudert at gcc dot gnu dot org 2008-04-21 13:04 ` ktietz at gcc dot gnu dot org 2008-07-10 0:50 ` nightstrike at gmail dot com 2009-08-21 17:25 ` ktietz at gcc dot gnu dot org 2009-08-25 10:36 ` ktietz at gcc dot gnu dot org [not found] <bug-34315-4@http.gcc.gnu.org/bugzilla/> 2010-10-02 11:50 ` ktietz 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=20080216204651.26713.qmail@sourceware.org \ --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).