public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bdavis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42517] -fcheck=recursion does not work with -fopenmp Date: Mon, 04 Jan 2010 17:55:00 -0000 [thread overview] Message-ID: <20100104175452.16407.qmail@sourceware.org> (raw) In-Reply-To: <bug-42517-16146@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from bdavis at gcc dot gnu dot org 2010-01-04 17:54 ------- Index: gcc/gcc/fortran/trans-decl.c =================================================================== --- gcc/gcc/fortran/trans-decl.c (revision 155625) +++ gcc/gcc/fortran/trans-decl.c (working copy) @@ -4330,6 +4330,7 @@ sym->name); recurcheckvar = gfc_create_var (boolean_type_node, "is_recursive"); TREE_STATIC (recurcheckvar) = 1; + DECL_TLS_MODEL (recurcheckvar) = decl_default_tls_model (recurcheckvar); DECL_INITIAL (recurcheckvar) = boolean_false_node; gfc_add_expr_to_block (&block, recurcheckvar); gfc_trans_runtime_check (true, false, recurcheckvar, &block, -- bdavis at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bdavis at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42517
next prev parent reply other threads:[~2010-01-04 17:55 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-27 18:16 [Bug fortran/42517] New: Bogus runtime error with -fopemp -fcheck=recursion janus at gcc dot gnu dot org 2009-12-27 18:39 ` [Bug fortran/42517] Bogus runtime error with -fopenmp -fcheck=recursion janus at gcc dot gnu dot org 2009-12-29 19:30 ` janus at gcc dot gnu dot org 2009-12-29 20:19 ` [Bug fortran/42517] -fcheck=recursion does not work with -fopenmp janus at gcc dot gnu dot org 2010-01-04 7:31 ` burnus at gcc dot gnu dot org 2010-01-04 14:23 ` rguenth at gcc dot gnu dot org 2010-01-04 16:16 ` burnus at gcc dot gnu dot org 2010-01-04 17:55 ` bdavis at gcc dot gnu dot org [this message] 2010-01-04 18:41 ` hjl dot tools at gmail dot com 2010-01-04 22:36 ` hjl dot tools at gmail dot com 2010-01-05 14:16 ` burnus at gcc dot gnu dot org 2010-04-19 11:25 ` dominiq at lps dot ens dot fr 2010-04-21 12:25 ` burnus at gcc dot gnu dot 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=20100104175452.16407.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: 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).