public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/55399] New: pch tests fail on mips-mti-linux-gnu target Date: Mon, 19 Nov 2012 21:36:00 -0000 [thread overview] Message-ID: <bug-55399-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55399 Bug #: 55399 Summary: pch tests fail on mips-mti-linux-gnu target Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: pch AssignedTo: unassigned@gcc.gnu.org ReportedBy: sje@gcc.gnu.org CC: joseph@codesourcery.com Starting with r192715 a large number (almost all) of the pch tests started failing on the mips-mti-linux-gnu target. I have verified that they pass using r192714. I think the problem has something to do with when/where/if pch_cpp_save_state() is called but I am not sure. I noticed that done_preinclude is an uninitialized global variable, but explicitly initializing it to false did not fix the problem. I have no idea why this would not be affecting other targets as I don't see any MIPS specific changes in this patch but I have not seen it on other targets. The patch that caused the regression is mostly in libcpp: 2012-10-23 Joseph Myers <joseph@codesourcery.com> * files.c (struct _cpp_file): Add implicit_preinclude. (pch_open_file): Allow a previously opened implicitly included file. (_cpp_find_file): Add implicit_preinclude argument. Free file and do not call open_file_failed if implicit_preinclude. Store implicit_preinclude value. (_cpp_stack_include, _cpp_fake_include, _cpp_compare_file_date): Update calls to _cpp_find_file. (_cpp_stack_include): Handle IT_DEFAULT. (cpp_push_default_include): New. * include/cpplib.h (cpp_push_default_include): Declare. * init.c (cpp_read_main_file): Update call to _cpp_find_file. * internal.h (enum include_type): Add IT_DEFAULT. (_cpp_find_file): Update prototype.
next reply other threads:[~2012-11-19 21:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-19 21:36 sje at gcc dot gnu.org [this message] 2012-11-19 22:55 ` [Bug pch/55399] " joseph at codesourcery dot com 2012-11-19 23:53 ` sje at gcc dot gnu.org 2012-11-20 0:16 ` joseph at codesourcery dot com 2012-11-20 0:32 ` sje at gcc dot gnu.org 2012-11-20 0:44 ` joseph at codesourcery dot com 2012-11-21 21:29 ` sje at gcc dot gnu.org 2012-11-21 21:42 ` sje at gcc dot gnu.org 2015-06-12 11:59 ` jakub 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-55399-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: 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).