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 bootstrap/63995] Bootstrap error with -mmpx -fcheck-pointer-bounds
Date: Tue, 25 Nov 2014 13:04:00 -0000	[thread overview]
Message-ID: <bug-63995-4-jtqmhhMaxS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63995-4@http.gcc.gnu.org/bugzilla/>

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

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

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63995
> 
> --- Comment #3 from Ilya Enkovich <enkovich.gnu at gmail dot com> ---
> Patch removing duplicating bounds symbols is in review.  With this patch
> applied bootstrap goes till the end but there are lots of stage2 and stage3
> comparison error.  I looked into one of them and the difference is caused by
> '-gtoggle' option used for stage2 build and not used for stage3 build.

This means you are generating different code with -g vs. -g0 which is
forbidden.


  parent reply	other threads:[~2014-11-25 13:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 12:33 [Bug bootstrap/63995] New: " rguenth at gcc dot gnu.org
2014-11-20 16:10 ` [Bug bootstrap/63995] " enkovich.gnu at gmail dot com
2014-11-20 16:16 ` enkovich.gnu at gmail dot com
2014-11-25 13:04 ` rguenther at suse dot de [this message]
2014-11-25 15:06 ` enkovich.gnu at gmail dot com
2014-11-25 15:45 ` enkovich.gnu at gmail dot com
2014-11-26  8:05 ` enkovich.gnu at gmail dot com
2014-11-26 14:37 ` ienkovich at gcc dot gnu.org
2014-12-09  7:54 ` ienkovich at gcc dot gnu.org
2014-12-09 10:42 ` enkovich.gnu at gmail dot com
2015-04-16 14:06 ` 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-63995-4-jtqmhhMaxS@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).