public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: taneem@eyetap.org To: gcc-gnats@gcc.gnu.org Cc: taneem.ahmed@latticesemi.com Subject: c++/5928: parse error before `or' Date: Tue, 12 Mar 2002 13:36:00 -0000 [thread overview] Message-ID: <20020312212927.22270.qmail@sources.redhat.com> (raw) >Number: 5928 >Category: c++ >Synopsis: parse error before `or' >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Tue Mar 12 13:36:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Taneem Ahmed >Release: gcc version 2.96 >Organization: >Environment: Redhat 7.2 >Description: gcc generates parse error on the following legal code: #include <stdio.h> int func(int or){ return 0; } int main(int argc, char **argv){ int or = 1; func(or); return 0; } > gcc or_error.cpp or_error.cpp:3: parse error before `or' or_error.cpp: In function `int main (int, char **)': or_error.cpp:8: parse error before `or' or_error.cpp:9: parse error before `or' >How-To-Repeat: compile the code >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-c++src; name="or_error.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="or_error.cpp" I2luY2x1ZGUgPHN0ZGlvLmg+CgppbnQgZnVuYyhpbnQgb3IpewoJcmV0dXJuIDA7Cn0KCmludCBt YWluKGludCBhcmdjLCBjaGFyICoqYXJndil7CglpbnQgb3IgPSAxOwoJZnVuYyhvcik7CglyZXR1 cm4gMDsKfQo=
next reply other threads:[~2002-03-12 21:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-12 13:36 taneem [this message] 2002-03-12 13:56 Andrew Pinski 2002-03-12 14:13 nathan
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=20020312212927.22270.qmail@sources.redhat.com \ --to=taneem@eyetap.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=taneem.ahmed@latticesemi.com \ /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).