public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Geoffrey Keating <geoffk@apple.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/10757: Adding -fpic/-fPIC causes crash with PCH created without -fpic/-fPIC Date: Fri, 16 May 2003 07:36:00 -0000 [thread overview] Message-ID: <20030516073601.19128.qmail@sources.redhat.com> (raw) The following reply was made to PR other/10757; it has been noted by GNATS. From: Geoffrey Keating <geoffk@apple.com> To: gcc-prs@gcc.gnu.org, ghazi@caip.rutgers.edu, gcc-bugs@gcc.gnu.org, ljrittle@acm.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/10757: Adding -fpic/-fPIC causes crash with PCH created without -fpic/-fPIC Date: Thu, 15 May 2003 21:22:06 -0700 I have a report of a similar bug on Darwin. It's a PCH validation bug; it can't work if you build the PCH without -fpic but try to use it with -fpic, but the validation code doesn't check for this (which is tricky, because the reason it doesn't work is target-dependent, so we need to add some way for the target to save and validate some flags).
next reply other threads:[~2003-05-16 7:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-16 7:36 Geoffrey Keating [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-12 19:15 ljrittle
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=20030516073601.19128.qmail@sources.redhat.com \ --to=geoffk@apple.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).