public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57897] Target x86_64-w64-mingw32 failed with '-mno-fentry isn't compatible with SEH' Date: Thu, 12 Dec 2013 22:08:00 -0000 [thread overview] Message-ID: <bug-57897-4-gYrOp5TdfI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57897-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57897 --- Comment #9 from Kai Tietz <ktietz at gcc dot gnu.org> --- Issue is related to option -fasynchronous-unwind-tables option. Better said to option -fasynchronous-unwind-tables without -funwind-tables. Following sample can demonstrate issue pretty well: '#include <intrin.h> int a;' By compiling test by '$ x86_64-w64-mingw32-gcc -S -o t.s t_xmmintrin.c -O2 -fasynchronous-unwind-tables' I can reproduce the fentry message. By removing option -fasynchronous-unwind-tables, or adding -funwind-tables option message won't be displayed. By following patch for me the issue is solved: Index: i386.c =================================================================== --- i386.c (Revision 205859) +++ i386.c (Arbeitskopie) @@ -3698,6 +3698,10 @@ { if (opts->x_optimize >= 1 && !opts_set->x_flag_omit_frame_pointer) opts->x_flag_omit_frame_pointer = !USE_X86_64_FRAME_POINTER; + if (opts->x_flag_asynchronous_unwind_tables + && !opts_set->x_flag_unwind_tables + && TARGET_64BIT_MS_ABI) + opts->x_flag_unwind_tables = 1; if (opts->x_flag_asynchronous_unwind_tables == 2) opts->x_flag_unwind_tables = opts->x_flag_asynchronous_unwind_tables = 1; I will apply this patch to trunk soon, if there are no objections.
next prev parent reply other threads:[~2013-12-12 22:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-15 7:39 [Bug c++/57897] New: pragma dongsheng.song at gmail dot com 2013-07-15 7:47 ` [Bug c++/57897] Target x86_64-w64-mingw32 failed with '-mno-fentry isn't compatible with SEH' dongsheng.song at gmail dot com 2013-07-22 9:58 ` paolo.carlini at oracle dot com 2013-09-10 10:26 ` ktietz at gcc dot gnu.org 2013-12-06 0:05 ` ktietz at gcc dot gnu.org 2013-12-06 7:34 ` dongsheng.song at gmail dot com 2013-12-12 22:08 ` ktietz at gcc dot gnu.org [this message] 2013-12-13 9:00 ` rainer@emrich-ebersheim.de 2013-12-13 9:25 ` ktietz 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-57897-4-gYrOp5TdfI@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).