public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37902] [4.3 Regression] in_system_header bug
Date: Thu, 23 Oct 2008 12:41:00 -0000	[thread overview]
Message-ID: <20081023124026.30960.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37902-87@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from jakub at gcc dot gnu dot org  2008-10-23 12:40 -------
The regression has been introduced by PR32256, before that in_system_header
flag wasn't saved/restored in push_cfun/pop_cfun.
The issue seems to be that allocate_struct_function call in store_parm_decls
doesn't seem to have a corresponding set_cfun (NULL); call, so when push_cfun
during gimplification is called, it doesn't save in_system_header (as cfun is
already non-NULL) and more importantly, pop_cfun at the end of gimplification
pops to the same cfun, which means in_system_header remains 1 when leaving the
gimplifier and is then used by subsequent parsing of bar function.


-- 


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


  reply	other threads:[~2008-10-23 12:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 11:58 [Bug middle-end/37902] New: " jakub at gcc dot gnu dot org
2008-10-23 12:41 ` jakub at gcc dot gnu dot org [this message]
2008-10-27  2:01 ` [Bug middle-end/37902] " pinskia at gcc dot gnu dot org
2008-11-03 11:29 ` jakub at gcc dot gnu dot org
2009-01-24 10:26 ` rguenth at gcc dot gnu dot org
2009-08-04 12:43 ` rguenth at gcc dot gnu dot org
2010-05-22 18:26 ` rguenth at gcc dot gnu dot org
     [not found] <bug-37902-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 12:01 ` rguenth 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=20081023124026.30960.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).