public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin at netbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/58379] New: default mmap based implementation (mmap_gt_pch_get_address/mmap_gt_pch_use_address) is useless
Date: Tue, 10 Sep 2013 10:19:00 -0000	[thread overview]
Message-ID: <bug-58379-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 58379
           Summary: default mmap based implementation
                    (mmap_gt_pch_get_address/mmap_gt_pch_use_address) is
                    useless
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: martin at netbsd dot org

I may be misunderstanding the interface - but it looks to me like it lets the
kernel chose an arbitrary mapping address for different compiler invocations
but relies on the assumption that the returned address will be the same. If
not, the compiler fails with a fatal_error when trying to read a precompiled
header file ("had to relocate PCH").

I can not imagine a host system where this would work reliably (or even
typically twice in a row).

Please tell me I misunderstood, or consider disabling PCH support for host
platforms without host_hooks overriding this function.


             reply	other threads:[~2013-09-10 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 10:19 martin at netbsd dot org [this message]
2013-09-10 11:32 ` [Bug preprocessor/58379] " rguenth at gcc dot gnu.org
2013-09-10 13:13 ` martin at netbsd dot org
2021-12-08 18:21 ` pinskia 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-58379-4@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: 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).