public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/65384] New: Intel MPX does not support x32 Date: Wed, 11 Mar 2015 02:01:00 -0000 [thread overview] Message-ID: <bug-65384-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65384 Bug ID: 65384 Summary: Intel MPX does not support x32 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: doko at gcc dot gnu.org seen when enabling mpx and x32 multilibs looks like the configure.tgt is too permissive x86_64-*-linux* | i?86-*-linux*) libtool: compile: /home/packages/gcc/5/gcc-5-5-20150310/build/./gcc/xgcc -B/home/packages/gcc/5/gcc-5-5-20150310/build/./gcc/ - B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/s ys-include -isystem /home/packages/gcc/5/gcc-5-5-20150310/build/sys-include -mx32 -DHAVE_CONFIG_H -I. -I../../../../../src/libmp x/mpxwrap -I.. -fcheck-pointer-bounds -mmpx -fno-chkp-check-read -fno-chkp-check-write -fno-chkp-use-wrappers -fPIC -g -O2 -mx32 -c ../../../../../src/libmpx/mpxwrap/mpx_wrappers.c -fPIC -DPIC -o .libs/libmpxwrappers_la-mpx_wrappers.o ../../../../../src/libmpx/mpxwrap/mpx_wrappers.c:1:0: error: Intel MPX does not support x32 /* MPX Wrappers Library ^ ../../../../../src/libmpx/mpxwrap/mpx_wrappers.c:1:0: error: Intel MPX does not support x32 Makefile:363: recipe for target 'libmpxwrappers_la-mpx_wrappers.lo' failed make[11]: *** [libmpxwrappers_la-mpx_wrappers.lo] Error 1
next reply other threads:[~2015-03-11 2:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-11 2:01 doko at gcc dot gnu.org [this message] 2015-03-11 15:46 ` [Bug other/65384] " hjl.tools at gmail dot com 2015-03-12 11:16 ` ienkovich at gcc dot gnu.org 2015-03-12 11:29 ` ienkovich 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-65384-4@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).