public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ljrittle@acm.org To: gcc-gnats@gcc.gnu.org Subject: other/10757: Adding -fpic/-fPIC causes crash with PCH created without -fpic/-fPIC Date: Mon, 12 May 2003 19:15:00 -0000 [thread overview] Message-ID: <20030512184232.1422.qmail@sources.redhat.com> (raw) >Number: 10757 >Category: other >Synopsis: Adding -fpic/-fPIC causes crash with PCH created without -fpic/-fPIC >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon May 12 19:06:03 UTC 2003 >Closed-Date: >Last-Modified: >Originator: ljrittle@acm.org >Release: mainline 5/12 >Organization: >Environment: sol2.9 & ppclinux & i386-unknown-freebsd4.8 >Description: People on the libstdc++ mailing list found a problem with PCH and the -fpic flag that I traced to this root (multi-file) test case. >How-To-Repeat: ; echo >t.h ; echo >main.c 'int main() {}' ; g++ -o t.h.gch t.h ; g++ -include t.h -Winvalid-pch main.c ; g++ -include t.h -Winvalid-pch -fpic main.c main.c: In function `int main()': main.c:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. ; g++ -fpic main.c (Humm, at this point, I'd have thought that maybe something wasn't marked for PCH/GC properly in a region keyed by -fpic, but then I noticed:) ; g++ -fpic -o t.h.gch t.h ; g++ -include t.h -Winvalid-pch main.c cc1plus: warning: ./t.h.gch: not used because `__pic__' not defined ; g++ -include t.h -Winvalid-pch -fpic main.c I'm sorry, I have no time to debug this today. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-05-12 19:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-12 19:15 ljrittle [this message] 2003-05-16 7:36 Geoffrey Keating
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=20030512184232.1422.qmail@sources.redhat.com \ --to=ljrittle@acm.org \ --cc=gcc-gnats@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).