public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sezeroz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39063] libgcc2.c:mprotect() for mingw, incompatible pointer type warning
Date: Thu, 19 Mar 2009 17:50:00 -0000	[thread overview]
Message-ID: <20090319174952.503.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39063-17247@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from sezeroz at gmail dot com  2009-03-19 17:49 -------
The prototype for VirtualProtect() is known but the definition of DWORD is
not??
Hrmph. In any case, it should be fixed easily by changing DWORD into unsigned
int
which is what a DWORD is always defined as.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39063


  parent reply	other threads:[~2009-03-19 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 16:53 [Bug target/39063] New: " sezeroz at gmail dot com
2009-02-01 16:53 ` [Bug target/39063] " sezeroz at gmail dot com
2009-02-21  9:52 ` ktietz at gcc dot gnu dot org
2009-03-14 16:00 ` nightstrike at gmail dot com
2009-03-19 10:40 ` gerald at gcc dot gnu dot org
2009-03-19 14:52 ` hjl dot tools at gmail dot com
2009-03-19 17:50 ` sezeroz at gmail dot com [this message]
2009-04-13 11:55 ` sezeroz at gmail dot com

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=20090319174952.503.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: link
Be 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).