public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bowie dot owens at csiro dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/27746] ICE on openmp code when using _Pragma from macro Date: Wed, 24 May 2006 03:42:00 -0000 [thread overview] Message-ID: <20060524034211.1487.qmail@sourceware.org> (raw) In-Reply-To: <bug-27746-12330@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from bowie dot owens at csiro dot au 2006-05-24 03:42 ------- I found out about _Pragma from the following page (at the bottom): http://gcc.gnu.org/onlinedocs/gcc-4.1.0/gcc/Function-Attributes.html While it is not essential behaviour to allow _Pragma's to be generated from macros, there are cases where it would be very useful. In my case I would really like to be able to control the OpenMP directives that get included at a fine grained level without littering my code with #ifdef's. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27746
next prev parent reply other threads:[~2006-05-24 3:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-24 1:46 [Bug c++/27746] New: " bowie dot owens at csiro dot au 2006-05-24 1:47 ` [Bug c++/27746] " bowie dot owens at csiro dot au 2006-05-24 3:08 ` pinskia at gcc dot gnu dot org 2006-05-24 3:10 ` [Bug c/27746] " pinskia at gcc dot gnu dot org 2006-05-24 3:24 ` [Bug preprocessor/27746] " pinskia at gcc dot gnu dot org 2006-05-24 3:24 ` pinskia at gcc dot gnu dot org 2006-05-24 3:29 ` pinskia at gcc dot gnu dot org 2006-05-24 3:34 ` pinskia at gcc dot gnu dot org 2006-05-24 3:42 ` bowie dot owens at csiro dot au [this message] 2006-05-24 3:45 ` pinskia at gcc dot gnu dot org 2006-05-25 12:29 ` jakub at gcc dot gnu dot org 2006-05-25 15:47 ` jakub at gcc dot gnu dot org 2006-05-25 16:45 ` pinskia at gcc dot gnu dot org 2006-06-09 21:19 ` jakub at gcc dot gnu dot org 2006-06-09 21:27 ` jakub 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=20060524034211.1487.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).