public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/21512] New: build failure on ppc-apple-darwin5.5 in libcpp Date: Wed, 11 May 2005 11:09:00 -0000 [thread overview] Message-ID: <20050511110924.21512.fxcoudert@gcc.gnu.org> (raw) When compiling libcpp/init.c: ../../gcc/libcpp/init.c:59: parse error before `,' [9 times] This error happens on: TRIGRAPH_MAP s('=', '#') s(')', ']') s('!', '|') s('(', '[') s('\'', '^') s('>', '}') s('/', '\\') s('<', '{') s('-', '~') END which, once preprocessed, is: __extension__ const uchar _cpp_trigraph_map[255 + 1] = { [ '=' ] = '#' , [ ')' ] = ']' , [ '!' ] = '|' , [ '(' ] = '[' , [ '\'' ] = '^' , [ '>' ] = '}' , [ '/' ] = '\\' , [ '<' ] = '{' , [ '-' ] = '~' , }; The following minimal code: __extension__ const unsigned char _cpp_trigraph_map[255 + 1] = { [ '=' ] = '#' , [ ')' ] = ']' , [ '!' ] = '|' }; compiles fine on my linux box but gives 3 "parse error before `,'" on ppc-darwin5.5. A workaround seems to specify -DHAVE_DESIGNATED_INITIALIZERS=0. -- Summary: build failure on ppc-apple-darwin5.5 in libcpp Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: fxcoudert at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: ppc-apple-darwin5.5 GCC host triplet: ppc-apple-darwin5.5 GCC target triplet: ppc-apple-darwin5.5 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21512
next reply other threads:[~2005-05-11 11:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-11 11:09 fxcoudert at gcc dot gnu dot org [this message] 2005-05-11 11:15 ` [Bug preprocessor/21512] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-05-11 11:41 ` [Bug bootstrap/21512] " bonzini at gcc dot gnu dot org 2005-05-11 11:42 ` bonzini at gcc dot gnu dot org 2005-05-19 11:38 ` fxcoudert at gcc dot gnu dot org 2005-06-26 18:17 ` pinskia at gcc dot gnu dot org 2005-07-08 1:35 ` mmitchel at gcc dot gnu dot org 2005-07-18 9:40 ` bonzini at gcc dot gnu dot org 2005-08-09 18:59 ` pinskia at gcc dot gnu dot org 2005-08-09 20:23 ` fxcoudert at gcc dot gnu dot org 2005-08-09 20:26 ` pinskia 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=20050511110924.21512.fxcoudert@gcc.gnu.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).