From: niXman <i.nixman@autistici.org>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: error building trunk as MinGW-W64
Date: Fri, 13 Dec 2013 22:16:00 -0000 [thread overview]
Message-ID: <248e4bc09c7bdadae52a8088877db3e5@autistici.org> (raw)
In-Reply-To: <891ecad50af6767bf8643f27c76db39e@autistici.org>
niXman 2013-12-11 00:53:
> Hi,
>
> Two weeks earlier I have successfully built gcc-trunk as MinGW-W64,
> but now I faced with error when building rev. 205849.
>
> The error is:
> gcc-trunk/prev-gcc/include/ia32intrin.h:54:28: sorry, unimplemented:
> -mno-fentry isn't compatible with SEH
> #pragma GCC target("sse4.2")
>
>
> I have two questions:
> 1. why the error message says about 'isn't compatible with SEH',
> though gcc is configured for using SJLJ exceptions?
> 2. Hou can I solve this error?
Fixed at rev. 205957
--
Regards, niXman
___________________________________________________
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___________________________________________________
Another online IDE: http://liveworkspace.org/
prev parent reply other threads:[~2013-12-13 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 20:53 niXman
2013-12-12 11:11 ` niXman
2013-12-13 22:16 ` niXman [this message]
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=248e4bc09c7bdadae52a8088877db3e5@autistici.org \
--to=i.nixman@autistici.org \
--cc=gcc-help@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: link
Be 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).