public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/39279] [lto] - Werror in ../lto_trunk/gcc/lto/lto.c
Date: Fri, 17 Jul 2009 06:44:00 -0000 [thread overview]
Message-ID: <20090717064339.960.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39279-13830@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from rob1weld at aol dot com 2009-07-17 06:43 -------
(In reply to comment #2)
> Confirmed. The proposed fix is not correct, though, as the type of the first
> argument to munmap _is_ void* according to POSIX.
Thanks for applying the patch. I've not looked at 'LTO' source in a few
months, we could 'cast in the other direction' (fix everything else),
but I imagine _we_ had a reason not to fix this properly ...
People need to test their code on a few versions of GCC (3.4.x & 4.x.x).
Thanks Ben & Rainer,
Rob
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39279
prev parent reply other threads:[~2009-07-17 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 19:07 [Bug bootstrap/39279] New: " rob1weld at aol dot com
2009-03-09 6:40 ` [Bug lto/39279] " rob1weld at aol dot com
2009-07-09 0:14 ` bje at gcc dot gnu dot org
2009-07-15 0:49 ` bje at gcc dot gnu dot org
2009-07-17 6:44 ` rob1weld at aol 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=20090717064339.960.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).