public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57362] [4.8/4.9 Regression] unsupported __attribute__((target())) values appear to cause loop and/or pathological behavior Date: Wed, 22 May 2013 08:17:00 -0000 [thread overview] Message-ID: <bug-57362-4-LEWYu1zMrd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57362-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57362 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Known to work| |4.7.3 Version|unknown |4.8.1 Keywords| |ice-on-invalid-code Last reconfirmed| |2013-05-22 CC| |tmsriram at google dot com Ever confirmed|0 |1 Summary|unsupported |[4.8/4.9 Regression] |__attribute__((target())) |unsupported |values appear to cause loop |__attribute__((target())) |and/or pathological |values appear to cause loop |behavior |and/or pathological | |behavior Target Milestone|--- |4.8.1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Works fine with the C compiler, for the C++ compiler we ICE: ... lots of errors ... t.c:18:5: error: No dispatcher found for align-stringops int foo(void) { return 1; } ^ t.c:187:20: internal compiler error: Segmentation fault result = foo(); ^ 0xc647e5 crash_signal /space/rguenther/src/svn/gcc-4_8-branch/gcc/toplev.c:332 0x53f4cb contains_struct_check(tree_node*, tree_node_structure_enum, char const*, int, char const*) /space/rguenther/src/svn/gcc-4_8-branch/gcc/tree.h:3797 0x9b6742 build_fold_addr_expr_loc(unsigned int, tree_node*) /space/rguenther/src/svn/gcc-4_8-branch/gcc/fold-const.c:7693 0xf498fa add_condition_to_bb /space/rguenther/src/svn/gcc-4_8-branch/gcc/config/i386/i386.c:28536 0xf4a6d0 dispatch_function_versions /space/rguenther/src/svn/gcc-4_8-branch/gcc/config/i386/i386.c:28951 0xf4c178 ix86_generate_version_dispatcher_body /space/rguenther/src/svn/gcc-4_8-branch/gcc/config/i386/i386.c:29517 you cannot query for acceptable values by re-annotating the same decl. GCC 4.7 happily says ... t.c:176:5: error: redefinition of 'int foo()' t.c:2:5: error: 'int foo()' previously defined here t.c: At global scope: t.c:178:13: error: attribute(target("avx256-split-unaligned-store")) is unknown t.c: In function 'int foo()': t.c:178:5: error: redefinition of 'int foo()' t.c:2:5: error: 'int foo()' previously defined here t.c: At global scope: t.c:180:13: error: attribute(target("rtm")) is unknown t.c: In function 'int foo()': t.c:180:5: error: redefinition of 'int foo()' t.c:2:5: error: 'int foo()' previously defined here and does not ICE. Google folks - please have a look.
next prev parent reply other threads:[~2013-05-22 8:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-21 19:16 [Bug c++/57362] New: " mib.bugzilla at gmail dot com 2013-05-21 19:18 ` [Bug c++/57362] " mib.bugzilla at gmail dot com 2013-05-22 8:17 ` rguenth at gcc dot gnu.org [this message] 2013-05-22 23:46 ` [Bug c++/57362] [4.8/4.9 Regression] " tmsriram at google dot com 2013-05-31 10:58 ` jakub at gcc dot gnu.org 2013-07-11 23:07 ` tmsriram at google dot com 2013-07-11 23:31 ` paolo.carlini at oracle dot com 2013-07-31 20:12 ` jason at gcc dot gnu.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-57362-4-LEWYu1zMrd@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).