public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/33426] Support of #pragma ivdep Date: Fri, 25 Oct 2013 05:47:00 -0000 [thread overview] Message-ID: <bug-33426-4-mmGPDLRc0G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-33426-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33426 --- Comment #15 from Tobias Burnus <burnus at gcc dot gnu.org> --- Author: burnus Date: Fri Oct 25 05:47:25 2013 New Revision: 204047 URL: http://gcc.gnu.org/viewcvs?rev=204047&root=gcc&view=rev Log: 2013-10-25 Tobias Burnus <burnus@net-b.de> PR other/33426 * parser.c (cp_parser_iteration_statement, cp_parser_for, cp_parser_c_for, cp_parser_pragma): Handle IVDEP pragma. * g++.dg/parse/ivdep.C: New. * g++.dg/vect/pr33426-ivdep.cc: New. Added: trunk/gcc/testsuite/g++.dg/parse/ivdep.C trunk/gcc/testsuite/g++.dg/vect/pr33426-ivdep.cc Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/parser.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2013-10-25 5:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-33426-4@http.gcc.gnu.org/bugzilla/> 2010-11-02 20:16 ` gjunk at sapience dot com 2011-05-07 12:29 ` gjunk at sapience dot com 2011-07-17 7:56 ` vincenzo.innocente at cern dot ch 2013-10-24 16:25 ` burnus at gcc dot gnu.org 2013-10-24 16:43 ` burnus at gcc dot gnu.org 2013-10-25 5:47 ` burnus at gcc dot gnu.org [this message] 2013-10-25 5:50 ` burnus at gcc dot gnu.org 2013-10-27 7:40 ` burnus at gcc dot gnu.org 2013-10-30 18:53 ` burnus at gcc dot gnu.org 2007-09-13 21:03 [Bug c/33426] New: " gjunk at sapience dot com 2007-09-13 21:27 ` [Bug other/33426] " pinskia at gcc dot gnu dot org 2007-09-13 22:21 ` gjunk at sapience dot com 2007-09-19 21:34 ` gjunk at sapience dot com
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-33426-4-mmGPDLRc0G@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).