public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/41526] gimple bytecode streams are not portable between different hosts
Date: Wed, 30 Sep 2009 20:17:00 -0000 [thread overview]
Message-ID: <20090930201705.9490.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41526-91@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from dnovillo at gcc dot gnu dot org 2009-09-30 20:17 -------
More portability concerns from
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg02157.html
> +/* This needs to be included after config.h. Otherwise, _GNU_SOURCE will not
> + be defined in time to set __USE_GNU in the system headers, and strsignal
> + will not be declared. */
> +#include <sys/mman.h>
mmap and <sys/mman.h> are also not portable to all supported hosts (e.g.
MinGW). There should be configure tests and a suitable fallback.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526
next prev parent reply other threads:[~2009-09-30 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 19:37 [Bug lto/41526] New: " dnovillo at gcc dot gnu dot org
2009-09-30 19:50 ` [Bug lto/41526] " dnovillo at gcc dot gnu dot org
2009-09-30 20:17 ` dnovillo at gcc dot gnu dot org [this message]
2010-09-01 19:30 ` jsm28 at gcc dot gnu dot org
[not found] <bug-41526-4@http.gcc.gnu.org/bugzilla/>
2021-12-26 2:07 ` pinskia at gcc dot gnu.org
2022-05-18 12:43 ` rguenth at gcc dot gnu.org
2022-07-04 8:41 ` rguenth at gcc dot gnu.org
2022-07-04 9:03 ` rguenth at gcc dot gnu.org
2022-07-04 9:28 ` richard at weickelt dot de
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=20090930201705.9490.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).