public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/63994] Ada bootstrap fails with -fcheck-pointer-bounds -mmpx
Date: Wed, 26 Nov 2014 15:51:00 -0000	[thread overview]
Message-ID: <bug-63994-4-WBUsmDA66D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63994-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63994

--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 26 Nov 2014, enkovich.gnu at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63994
> 
> --- Comment #3 from Ilya Enkovich <enkovich.gnu at gmail dot com> ---
> (In reply to rguenther@suse.de from comment #2)
> > 
> > > TARGET_CFLAGS="-O2 -g -mmpx -fcheck-pointer-bounds" TARGET_CXXFLAGS="-O2 
> > -g -mmpx -fcheck-pointer-bounds" BOOT_CFLAGS="-O2 -g -mmpx 
> > -fcheck-pointer-bounds" /space/rguenther/src/svn/trunk/configure 
> > --enable-languages=all,obj-c++,ada,go
> > > make -j12  TARGET_CFLAGS="-O2 -g -mmpx -fcheck-pointer-bounds" 
> > TARGET_CXXFLAGS="-O2 -g -mmpx -fcheck-pointer-bounds" BOOT_CFLAGS="-O2 -g 
> > -mmpx -fcheck-pointer-bounds"
> 
> Building with these options I see Ada compiler is called with
> -fcheck-pointer-bounds.  Option is in c-family/c.opt and shouldn't be passed
> for Ada compiler.  
> 
> We should either not pass CFLAGS for Ada during build or filter language in the
> compiler.

Any reason why non-C-family languages cannot use MPX?

Richard.


  parent reply	other threads:[~2014-11-26 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-63994-4@http.gcc.gnu.org/bugzilla/>
2014-11-20 12:33 ` enkovich.gnu at gmail dot com
2014-11-20 12:54 ` rguenther at suse dot de
2014-11-26 14:57 ` enkovich.gnu at gmail dot com
2014-11-26 15:51 ` rguenther at suse dot de [this message]
2014-11-26 16:07 ` enkovich.gnu at gmail dot com
2014-11-27  9:32 ` rguenther at suse dot de
2014-11-27  9:46 ` enkovich.gnu at gmail dot com

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-63994-4-WBUsmDA66D@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: 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).