public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "regehr at cs dot utah dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/41774] New: ice: vector VEC(visibility,base) pop domain error, in pop_visibility at c-pragma.c:757 Date: Wed, 21 Oct 2009 00:34:00 -0000 [thread overview] Message-ID: <bug-41774-12544@http.gcc.gnu.org/bugzilla/> (raw) Obviously the input is malformed, but probably still should not ICE. regehr@john-home:~/volatile/tmp208$ current-g++ -O small.cpp small.cpp:2:27: internal compiler error: vector VEC(visibility,base) pop domain error, in pop_visibility at c-pragma.c:757 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. regehr@john-home:~/volatile/tmp208$ current-g++ -v Using built-in specs. COLLECT_GCC=current-g++ COLLECT_LTO_WRAPPER=/home/regehr/z/tmp/gcc-r153044-install/libexec/gcc/i686-pc-linux-gnu/4.5.0/lto-wrapper Target: i686-pc-linux-gnu Configured with: ../configure --enable-lto --prefix=/home/regehr/z/tmp/gcc-r153044-install --program-prefix=r153044- --enable-languages=c,c++ Thread model: posix gcc version 4.5.0 20091020 (experimental) (GCC) regehr@john-home:~/volatile/tmp208$ cat small.cpp namespace std __attribute__ ((__visibility__ ("default"))) { #pragma GCC visibility pop -- Summary: ice: vector VEC(visibility,base) pop domain error, in pop_visibility at c-pragma.c:757 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: regehr at cs dot utah dot edu GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41774
next reply other threads:[~2009-10-21 0:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-21 0:34 regehr at cs dot utah dot edu [this message] 2009-10-21 8:01 ` [Bug c++/41774] " jakub at gcc dot gnu dot org 2009-11-02 13:40 ` jakub at gcc dot gnu dot org 2009-11-02 13:58 ` 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=bug-41774-12544@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).