public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: angarcia@univalle.edu.co To: gcc-gnats@gcc.gnu.org Subject: c++/4320: Multidimensional arrays of constant strings does not work properly, when declared as static in the private part of a class. Date: Thu, 13 Sep 2001 13:56:00 -0000 [thread overview] Message-ID: <20010913205141.14535.qmail@sourceware.cygnus.com> (raw) >Number: 4320 >Category: c++ >Synopsis: Multidimensional arrays of constant strings does not work properly, when declared as static in the private part of a class. >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Sep 13 13:56:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: angarcia@univalle.edu.co >Release: Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.96/specs gcc version 2.96 20000731 (Linux-Mandrake 8.0 2.96-0.48mdk) >Organization: >Environment: Mandrake 8.0 on AMD K-6 >Description: Multidimensional arrays of constant strings does not work properly, when declared as static in the private part of a class. - If 'const' is supressed, then it works ok. - If declared as local variable in main(), then it works ok. - If the array is unidimensional, then it works ok. >How-To-Repeat: g++ main.cpp ./a.out >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-c++src; name="main.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="main.cpp" LyoKICBQcm9ibGVtOgogIE11bHRpZGltZW5zaW9uYWwgYXJyYXlzIG9mIGNvbnN0YW50IHN0cmlu Z3MgZG9lcyBub3Qgd29yayBwcm9wZXJseSwgd2hlbiBkZWNsYXJlZCBhcyBzdGF0aWMgaW4gdGhl IHByaXZhdGUgcGFydCBvZiBhIGNsYXNzLgogIElmICdjb25zdCcgaXMgc3VwcmVzc2VkLCB0aGVu IGl0IHdvcmtzIG9rLgoKQ29tcGlsZXIgdmVyc2lvbjoKZysrIC12ClJlYWRpbmcgc3BlY3MgZnJv bSAvdXNyL2xpYi9nY2MtbGliL2k1ODYtbWFuZHJha2UtbGludXgvMi45Ni9zcGVjcwpnY2MgdmVy c2lvbiAyLjk2IDIwMDAwNzMxIChMaW51eC1NYW5kcmFrZSA4LjAgMi45Ni0wLjQ4bWRrKQoqLwoK I2luY2x1ZGUgPGlvc3RyZWFtLmg+CiNpbmNsdWRlIDxzdHJpbmc+CnVzaW5nIG5hbWVzcGFjZSBz dGQ7CgpjbGFzcyBUZXN0CnsKICBwcml2YXRlOgogICAgLy8gaWYgSSBzdXByZXNzICdjb25zdCcg dGhlbiBpdCB3b3JrcyBvazoKICAgIHN0YXRpYyBjb25zdCBzdHJpbmcgYXJyYXlbMl1bMl07CiAg cHVibGljOgogICAgVGVzdCgpCiAgICB7CiAgICAgIGNvdXQgPDwgYXJyYXlbMF1bMF0gPDwgZW5k bDsgICAgLy8gUHJpbnRzICJPbmUiCiAgICAgIGNvdXQgPDwgYXJyYXlbMF1bMV0gPDwgZW5kbDsg ICAgLy8gUHJpbnRzICJPbmUiLiBXcm9uZy4gSXQgbXVzdCBiZSAiVHdvIgogICAgICBjb3V0IDw8 IGFycmF5WzFdWzBdIDw8IGVuZGw7ICAgIC8vIFByaW50cyAiVGhyZWUiCiAgICAgIGNvdXQgPDwg YXJyYXlbMV1bMV0gPDwgZW5kbDsgICAgLy8gUHJpbnRzICJUaHJlZSIuIFdyb25nLiBJdCBtdXN0 IGJlICJGb3VyIgogICAgfQp9OwoKLy8gaWYgSSBzdXByZXNzICdjb25zdCcgdGhlbiBpdCB3b3Jr cyBvazoKY29uc3Qgc3RyaW5nIFRlc3Q6OmFycmF5WzJdWzJdID0KICB7CiAgICB7ICJPbmUiLCAi VHdvIiB9LAogICAgeyAiVGhyZWUiLCAiRm91ciIgfSwKICB9OwoKCgppbnQgbWFpbihpbnQgYXJn YywgY2hhciAqYXJndltdKQp7CiAgVGVzdCB0ZXN0OwogIHJldHVybiAwOwp9Cg==
next reply other threads:[~2001-09-13 13:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-13 13:56 angarcia [this message] 2001-12-15 10:23 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=20010913205141.14535.qmail@sourceware.cygnus.com \ --to=angarcia@univalle.edu.co \ --cc=gcc-gnats@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).